Adding a rpm spec file to httpd v2.0

[Graham Leggett <mi...@sharp.fm>]

Hi all,

A while back it was discussed whether an rpm spec file could be added to 
httpd v2.0 (and v2.1), and people said it was a good idea, but then it 
fell by the wayside. I am looking at this again, and have a number of 
questions.

When a source tarball is created, there should be an httpd.spec file in 
the root of the tarball directory so that rpm -tb httpd-version.tar.gz 
will work. This spec file needs to have the httpd version included in it.

Does anyone have a quick howto on how the httpd version gets embedded 
into the tarball when it is rolled? I looked at the 
build/httpd_roll_release file but I could not see where it was done.

Regards,
Graham
-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."

Re: Adding a rpm spec file to httpd v2.0

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

At 03:29 AM 3/27/2003, Graham Leggett wrote:
>William A. Rowe, Jr. wrote:
>
>>Finally an answer I can contribute to from Win32's perspective ;-)
>>We extract the version into all compiled binaries by invoking build/win32ver.awk,
>>with a command such as;
>>awk -f ./build/win32/win32ver.awk libhttpd.dll "Apache HTTP Server Core"  ./include/ap_release.h > .\build\win32\libhttpd.rc
>>Feel free to look at win32ver.awk as to how we extract the version from
>>ap_release.h.
>
>When is this done though?

It's a dependency of each library, e.g. the example above is a dependency
for building libhttpd.dll.  I actually do a full build locally, export makefiles,
and then copy all of the generated .rc, .mak and .dep files from that full 
build tree into a clean distribution tree for release .zip files.

>Ideally I would like to set up httpd.spec when buildconf is run, I assume that somewhere in buildconf the version number is embedded somewhere. Can you give me more details as to where this is done?

You can't really create the .spec until all the targets are determined, can you?
That would mean waiting for ./configure.  If you wanted to hack something to
the source tarball as part of ./buildconf, seems like a simple enough patch.

Re: Adding a rpm spec file to httpd v2.0

[Graham Leggett <mi...@sharp.fm>]

William A. Rowe, Jr. wrote:

> Finally an answer I can contribute to from Win32's perspective ;-)
> We extract the version into all compiled binaries by invoking build/win32ver.awk,
> with a command such as;
> 
> awk -f ./build/win32/win32ver.awk libhttpd.dll "Apache HTTP Server Core"  ./include/ap_release.h > .\build\win32\libhttpd.rc
> 
> Feel free to look at win32ver.awk as to how we extract the version from
> ap_release.h.

When is this done though?

Ideally I would like to set up httpd.spec when buildconf is run, I 
assume that somewhere in buildconf the version number is embedded 
somewhere. Can you give me more details as to where this is done?

Regards,
Graham
-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."

Re: Adding a rpm spec file to httpd v2.0

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

At 10:46 AM 3/26/2003, Graham Leggett wrote:

>Does anyone have a quick howto on how the httpd version gets embedded into the tarball when it is rolled? I looked at the build/httpd_roll_release file but I could not see where it was done.

Finally an answer I can contribute to from Win32's perspective ;-)
We extract the version into all compiled binaries by invoking build/win32ver.awk,
with a command such as;

awk -f ./build/win32/win32ver.awk libhttpd.dll "Apache HTTP Server Core"  ./include/ap_release.h > .\build\win32\libhttpd.rc

Feel free to look at win32ver.awk as to how we extract the version from
ap_release.h.

Bill