I can't find the original message, so I'll have to do some indirect answering.
Lamar Owen <lamar.owen@wgcr.org> writes:
> Jan Dittberner wrote:
> > Lamar Owen wrote:
> > > > For the Mandrake stuff, perhaps we can do it as a team; the first
> > > > important step is for someone to start "babysitting" it, just building
> > > > and posting the RPMs from Lamar's sources, then posting the results at
> > > > Mandrake's web site.
>
> > > Yes! Try a simple --rebuild of my SRPM first -- then, send me a diff of
>
> > I did so, I build packages for Mandrake. Your SPEC file is great and
> > I had only to do some little changes for full Mandrake compliance.
>
> > - pack all source files with bzip2, even those you left
> > uncompressed
If the postgresql team releases bz2 - good. If there is no file
ftp://foo.bar.com/xyzzy.tar.bz2
but just
ftp://foo.bar.com/xyzzy.tar.gz
then using that URL is just lying. Don't do that. Surely Mandrake
doesn't do that?
> > - extract the .jar files and the init/logrotate scripts at their destination
> > - bzip2 all man pages
Don't. This should be handled automatically with the "--buildpolicy"
flag[1]. like we do. Besides, bzipping man pages is in the "use bzip2,
even though there is no point in it" category.
[1] Like this: "rpm -ba --buildpolicy redhat postgresql.spec"
No need to strip or compress explicitly.
--
Trond Eivind Glomsrød
Red Hat, Inc.