[postgis-devel] PSC Vote: Get rid of micro in PostGIS Extension scripts (and comments from others)

[Sandro Santilli]

On Wed, Jul 06, 2022 at 01:09:37PM -0400, Greg Troxel wrote:
> "Regina Obe" <lr at pcorp.us> writes:
> 
> > The problem with that solution is that it presumes you are overlaying
> > installs.
> > Many packagers (and people for that matter) uninstall the old version and
> > then install the new.
> > In pg_upgrade, there is NO old install.
> >
> > So you will not have a postgis--2.0.0--ANY.sql  lying around to use.
> 
> A very good point - indeed packaging systems have a manifest of what was
> installed before and remove the old files.  I am not sure that is
> always, but I would view a packaging system that left a
> (non-user-configuration) file from a deinstalled package to be buggy.

Ok, I see, then unless we'll consider upgrade scripts "configuration"
we'd still need to always install upgrade scripts for all paths of all
old releases. And there's no way the -MAX thing will save us from
referencing each and every possible older release as we'd still need
the path OLD.SPECIFIC.THING--MAX.OR.ANY ...

Given the above I don't see a way to reduce pollution other than
avoiding the OLD.SPECIFIC.THING--CURRENT.INSTALL.VERSION but rather
alwyas override the same OLD.SPECIFIC.THING--ANY path, which you
mentioned, Regina, as being something that packagers don't like.
Do you confirm, Greg, that you don't want a file like:

  postgis--2.0.0--ANY.sql

Installed by multiple contending versions of PostGIS ?
The idea is that file would mostly always have the same content
(no content at all).

--strk;

  Libre GIS consultant/developer
  https://strk.kbt.io/services.html