making httpd v2.0.50 binary RPMS available

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

Hi all,

I have built binary RPMs for i386 and ppc of httpd-2.0.50. In order to 
get the RPMs to build at all, I used the RPM spec file that includes the 
missing files fixes + db4-devel change included in v2.0.51-dev against 
the standard httpd-2.0.50-tar.gz archive as released.

Should these resulting RPM files be made available in the binaries 
directory, or should we wait till v2.0.51?

Regards,
Graham
--

Re: making httpd v2.0.50 binary RPMS available

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

Sander Temme wrote:

> Well, the only delta is the SPEC file, right?

Correct.

> How about publishing your 
> RPMs, pointing out that they represent a small delta w.r.t. the 2.0.50 
> tag, and rolling a patch representing those changes?
> 
> That way, we have viable RPMs available, and if folks want to roll their 
> own they'd simply apply the patch to get up to parity with what you did.

I have created a signed SRPM file, which is the original v2.0.50 source 
file + the spec file used to create the RPM (the spec file including the 
delta, the source file being the version as released and signed by ASF).

What I can do is provide the SRPM and a README explaining the story.

Regards,
Graham
--

Re: making httpd v2.0.50 binary RPMS available

[Sander Temme <sa...@temme.net>]

On Jul 1, 2004, at 3:25 PM, Graham Leggett wrote:

> Should these resulting RPM files be made available in the binaries 
> directory, or should we wait till v2.0.51?

Well, the only delta is the SPEC file, right? How about publishing your 
RPMs, pointing out that they represent a small delta w.r.t. the 2.0.50 
tag, and rolling a patch representing those changes?

That way, we have viable RPMs available, and if folks want to roll 
their own they'd simply apply the patch to get up to parity with what 
you did.

S. (Just my 2c)

-- 
sander@temme.net              http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF