Re: Markus Wanner 2017-06-15 <ec5beb31-d396-4b2c-6cf8-ae9a7a5a41fc@bluegap.ch>
> > I thought the "postgis scripts" package was for updating the server's
> > postgis version?
>
> Correct, it's not strictly needed after CREATE EXTENSION, but the
> extension keeps working without it.
>
> While the *-scripts packages conflict against each other, the extension
> packages (postgresql-X.Y-postgis-M.N) do not, allowing users to upgrade
> without breaking existing installations.
Ah right, I remembered that part, but not that *-scripts do conflict.
> > "This package contains SQL scripts to upgrade from earlier PostGIS
> > versions for PostgreSQL 9.6 as well as Perl utility scripts."
>
> As this hasn't quite clarified it, can you maybe provide a better
> description?
It doesn't say that it is needed for the initial installation as well.
From UX viewpoint, it would be nice if "apt-get install
postgresql-9.6-postgis-2.3" just worked. My idea would be:
Package: postgresql-9.6-postgis-2.3
Depends: postgresql-9.6-postgis-scripts
This means that each postgis N.N version can ship a new version of
-scripts which would then overwrite the older versions. Provided that
the *.sql files for older postgis versions are still shipped in newer
releases, users could even install older postgis extensions by using
the correct CREATE EXTENSION ... VERSION command. Unfortunately that's
not the case [1].
[1] https://packages.debian.org/sid/all/postgresql-9.6-postgis-2.3-scripts/filelist
Or maybe all scripts packages should have Replaces: instead of
Conflicts:. (Though that doesn't scale I think)
Hrm. I'll try discussing that with the colleagues here, maybe they
have an idea.
Christoph