* Martin Pitt ([email protected]) 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
signature.asc
Description: Digital signature
