[Pkg-postgresql-public] Non-versionized extension package aliases?

Christoph Berg myon at debian.org
Fri Aug 25 19:44:04 UTC 2017


Re: Ole Streicher 2017-08-25 <4d81f803-b514-9c95-421e-173d7f21d65f at debian.org>
> I first need to see how a postgresql upgrade would work at all in my
> case (still getting familar with the package). I could imagine that it
> helps to have an additional metapackage posgresql-default-pgsphere
> (depending on a postgersql-default package), and then have the dependency
> 
> Depends: postgresql-default-pgsphere | postgresql-pgsphere
> 
> in the main server package. That would install (and keep) by default the
> latest package, but also allows to work with a predefined specific
> version if the user wants this.

That should work I think.

> There is, however still some need for discussion with the gavodach upstream.
> 
> How is this solved for other applications that need postgresql + extensions?

Unsolved so far. There's a discussion in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857770

I'm still unsure if adding yet more packages next to the already very
small PG extension packages is the right step. But maybe I should just
give in and do it that way...

Christoph



More information about the Pkg-postgresql-public mailing list