[Pkg-postgresql-public] Dropping postgresql 8.3 for squeeze

Stephen Frost sfrost at snowman.net
Wed Dec 30 19:05:15 UTC 2009


* Martin Pitt (mpitt at debian.org) wrote:
> Dimitri Fontaine [2009-12-30 14:17 +0100]:
> > The problem for the maintainer is having to edit a package, hence do
> > some testing and QA again, when there's absolutely NO value in doing so,
> > neither for the maintainer, the extension or its users.
> 
> That's only true if the change is to drop a supported version. If one
> is added (like a new major version is packaged), then you do need to
> adapt your package and test etc., since it will most likely not even
> build against the newer server version.

It might, but of course, even if it *did* build against the newer server
version, you should definitely test to make sure it behaves correctly..

I don't like the idea of having one binary package with multiple PG
versions, that's just a bad idea all around in my view.  You could make
your debian/control file dynamically generated using scripts and the
script Martin has to list what major versions exist, but that'd only be
done as part of a maintainer upload (in other words, the buildds
shouldn't dynamically build it, I don't think).

You could still maintain a single source package..

	Stephen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20091230/0acd4033/attachment.pgp>


More information about the Pkg-postgresql-public mailing list