Tom Lane wrote:
Meanwhile, it's not the RPMs' place to editorialize on which contrib
items are useful. Package 'em all, unless we hit build problems.
Interesting point of view :-). Going into 'Uncle Martin' mode (obscure
joke alert...).
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
It has been requested that I ship prebuilt contrib items in the 7.1
RPMset. Currently, the source code of the whole contrib tree is being
shipped in the main RPM as documentation, but only autoinc and refint
are being prebuilt (as part of the -test subpackage).
I have had three different types
Now that pg_dump pg_restore can handle large objects, the only need
for pg_dumplo is for migrating large objects from prior versions. I
personally cannot see it being used on a day to day basis, but I'm
looking at it from a narrow perspective. If it is a separate package,
it can easily be
Randy Hall wrote:
I think the cleanest way to provide the contrib programs is to build a
postgresql-contrib with _everything_ in it. Those people who need a
specific binary will be able to get it from /usr/lib/pgsql (or wherever)
and the distiction between core and contrib programs will
On Thu, 25 Jan 2001, Lamar Owen wrote:
But, in the instance of pg_dumplo -- can I get some ideas on it? Should
it be shipped as a separate package, or in the -server subpackage, or??
..ignore it. Not needful for 7.1, but can be interesting for 7.1
(old DB users can found it directly on
Oliver Elphick wrote:
Randy Hall wrote:
I think the cleanest way to provide the contrib programs is to build a
postgresql-contrib with _everything_ in it. Those people who need a
specific binary will be able to get it from /usr/lib/pgsql (or wherever)
and the distiction between
Lamar Owen [EMAIL PROTECTED] writes:
I think the cleanest way to provide the contrib programs is to build a
postgresql-contrib with _everything_ in it.
This is what I do for the Debian release.
Precedent set; precedent followed. I'll be hopefully packaging the
_entire_ contrib tree :-)
Peter Eisentraut [EMAIL PROTECTED] writes:
But, in the instance of pg_dumplo -- can I get some ideas on it? Should
it be shipped as a separate package, or in the -server subpackage, or??
It shouldn't be packaged at all because it's not necessary. (pg_dump
dumps large objects.)
The reason
