Re: Building PostgreSQL 7.0.1 documentation

Thomas Lockhart wrote:
> > > > I think I could test Mandrake RPMS from time to time.
> > > Do you work with the cooker folks? If so, then perhaps you could
> > > test and post Mandrake-specific RPMs which I've built? That would be
> > > a big help...
> > I'm not actually running the cooker distro, but I often commit
> > RPMS to the cooker. I will upgrade to 7.1 next week, so that I'm
> > not that far from the cooker. I had some contact with Lenny Cartier
> > (Mandrakesoft) and think he would accept me as a maintainer for
> > postgresql.
> > I would post your RPMS if you want.

> Great! I'm cc'ing Lamar Owens, who is the primary Redhat RPM maintainer.
> My last try at building pg-7.0 RPMs for Mandrake from Lamar's RH
> .src.rpm was a complete success with no additional patches required,
> though I have not had a chance to try the pg-7.0.2 RPM build and have
> not posted the results.

Interesting to see any differences, as the spec file itself has changed
some since the 7.0 series. I am trying to make this spec file buildable
on more than just RedHat -- so, testers are more than welcome. I
already am getting contributions for at least one non-RedHat
distribution for PowerPC from Murray Todd Williams (which RPM's I am
putting on ftp.postgresql.org) The more the merrier! The goal, of
course, is a single source RPM that everybody simply rebuilds, which
spec file simply Does The Right Thing (TM) for each distribution. I am
very grateful to the fine folks at RedHat for their help in making the
portability goal a little closer.

> 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
what it takes to get it to build right (including policy-type things,
such as bzip instead of gzip, or pgcc instead of egcs, or different
initscripts directory structure, etc.). Be sure to include any other
patches that may need to be included, and I'll try to get things
incorporated right away. As I only have RedHat 6.2+ boxen at the moment
(soon to get access to a SPARC, hopefully), I can only build and test on
them.

I was at one point going to get and install SuSE, Mandrake, Caldera, AND
RedHat all on one box, but that plan proved unweildy at best. Better to
get a SuSE person, a Mandrake (since Mandrake is diverging more and more
from its RedHat roots) person, and a Caldera person to be that
distribution's 'expert', who then helps me take the RedHat SRPM and
massage it to rebuild smoothly on each distribution. Plus, we can then
get people with Alphas, SPARCs, PPC's, or even IA-64's to do builds and
suggest changes. As well as getting reports from other RPM-based
distributions....

Also, when submitting patches to the spec file, include a copy of the
output of 'rpm --showrc', so I can see what kind of RPM environment you
have.

> btw, Lamar, can we put the .ps.gz doc files into the RPM distro, if you
> haven't already done so? Or should we break them out into separate RPMs,
> say for hardcopy and hardcopy-A4 or something like that?

I can, if that's what's wanted. I don't have a preference as to whether
it's still in the main package, or in a separate docs package, as, prior
to 7.0.1 the postscript stuff was in the main package. Just let me know
where the source .ps.gz files need to come from, so I don't get the
wrong ones. :-)

It would be preferable to have a versioned tarball of them available, as
there are already a larger number of source files in the RPM than I
would like.

Let me know....

--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11