On Wed, Dec 30, 2009 at 09:06:38PM +0100, Dimitri Fontaine wrote:
> Martin Pitt <mpitt@debian.org> writes:
>
> > Dimitri Fontaine [2009-12-30 10:52 +0100]:
> >> That's why I proposed having a single binary package for any extension,
> >> embedding support for more than one major version of PostgreSQL. That
> >> would match how the code is maintained.
> >
> > That would be a major regression wrt. upgrades, though, since an
> > upgrade from e. g. etch (8.1) to lenny (8.3) would upgrade
> > postgresql-foo and thus the 8.1 extension wouldn't be available any
> > more. With postgresql-foo-{8.1,8.3} you can install both side by side.
>
> Yeah. I'm too much into trying to have this deprecation policy in order
> to have all upstream maintained debian packages into debian stable it
> seems.
>
> Let's pursue the debian/control.in all automated build-depends and
> dynamic binary packages list idea then.
I'll adopt whatever the consensus is once agreed upon in my
postgresql-debversion package. I can also put in conditionals
to make it build with older versions again, but I'd like a
pointer to an example to see what's needed to conditionally
build < 8.4.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
Attachment:
signature.asc
Description: Digital signature