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

[Ole Streicher]

Hi Christoph,

On 25.08.2017 21:44, Christoph Berg wrote:
> 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...

In principle, one could do it in the same way as the Python3 packages
are maintained: combine the extension binaries for all postgresql
versions into a single package, and request a binNMU every time a new
postgresql version is uploaded (or an old one is removed). This would
also remove the need of d/control.in preprocessing. Since the extension
packages are small, the impact in disk space is negligible.

[... just reading #857770...]

I seem just to second Antonio's suggestion; and I also think it is
manageable; in the same manner as for Python3 (where I know it from), or
Ruby (which was Antonios example). Probably one could borrow some
strategies from there.

Best regards

Ole