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

[Ole Streicher]

Hi Christoph,

On 25.08.2017 20:36, Christoph Berg wrote:
> Re: Ole Streicher 2017-08-25 <fa5d33d0-1ecd-be7b-a171-ff9ad02613ef at debian.org>
>> Is there already a solution for this? Shall I use
>>
>> Provides: postgresql-pgsphere
>>
>> for all versionized extension packages?
> 
> Makes sense I think.

Thank you for the confirmation. I will add this to q3c and pgsphere.

> Note that it doesn't make PostgreSQL upgrades work, e.g. if you switch
> from jessie to stretch, it won't automatically pull in
> postgresql-9.6-pgsphere if you had postgresql-9.4-pgsphere installed
> before, as both provide postgresql-pgsphere. We'd need real meta
> packages for that, but that would mean even more .debs, which I'd be
> reluctant to add.

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.

There is, however still some need for discussion with the gavodach upstream.

How is this solved for other applications that need postgresql + extensions?

Best regards

Ole