Changes between Version 11 and Version 12 of PostGISExtensionPaths


Ignore:
Timestamp:
Feb 11, 2022, 11:18:52 AM (2 years ago)
Author:
robe
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • PostGISExtensionPaths

    v11 v12  
    9292{{{
    9393:
    94 postgis--3.1MAX--3.3MAX.sql
    95 postgis--3.2MAX--3.3MAX.sql
    96 postgis--3.3MAX--3.3.0.sql
    97 postgis--3.3.0--3.3MAX.sql
     94postgis--3.0.3--3.3.X.sql
     95postgis--3.0.5--3.3.X.sql
     96postgis--3.0.X--3.3.X.sql
     97postgis--3.1.X--3.3.X.sql
     98postgis--3.1.4--3.3.X.sql
     99postgis--3.1.5--3.3.X.sql
     100postgis--3.2.X--3.3.X.sql
     101postgis--3.3.X--3.3.0.sql
    98102}}}
    99103----
    … …  
    1021061. We are staying between the lines. Respecting known practices, but still having much lighter weight scripts.
    1031072. A little less clutter, but we are relying on the user having the old version still installed so that they have a chain
    104 postgis--<old-version-minor-micro>--<old-version-minor>MAX.sql
     108postgis--<old-version-minor>MIN--<old-version-minor>MIN.sql
    1051093. An easier release cycle since extensions/updateable.mk doesn't need to list the prior micros.
    1061104. No change in upgrade extension workflow for packagers (or users who think of PostGIS as any other extension).