Re: PostgreSQL 7.4.1 and pgdb.py

On Sun, 8 Feb 2004, Manuel Tejada wrote:
>
> > Lamar Owen wrote:
> > > Since I don't necessarily keep up with what is going on in the Python
> client
> > > world, would people enlighten me as to which python client would be best
> to
> > > build RPMs for? I'm going to pull the python subpackage out of the main
> set,
> > > but I really would like to roll a set for the python clients, unless the
> > > maintainers of those now out of the main tarball clients have their own
> RPMs.
>
> As a user of PostgreSQL I totally agree with Gaetano Mendola.
> There is no reason to pull the python subpackage out of the main set,
>

The decision to remove all interfaces from the main CVS tree was made in
part to remove the responsibility of the core developers to maintain the
build systems for various components and try to make sure that bugs and
new backend functionality were addressed. While this allows core
developers to focus solely on the backend it puts a lot of pressure on the
packagers to track the various components they are now distributing.
This is not the first packaging problem and it won't be the last if we
rely on a very busy package maintainer to track each independent project.
The only people who really know which version needs to go into an package
are the projects' maintainers.

Asking the interface projects to build and distribute their own packages
is not going to work because they are not likely to have all of the
requirements the existing packagers already have: expertise with the
packaging system, access to machines to build this on a variety of
platforms, and contacts with the upstream package distributors.

Perhaps a system where each project maintainer could register the correct
version of their package to go with each server version. This way in
addition to the hackers email that goes out saying "we're planning on
making the 7.X.X release on Monday" this would also go out to the project
maintainers who would then produce a new version if necessary and register
it on a website somewhere. Then when a packager is ready to produce a
package he can check the website and immediately find for all packages the
correct version of the package to distribute.

Lamar, Oliver, interface maintainers, and others would that be useful?

Kris Jurka