Changes between Version 11 and Version 12 of PostGISExtensionPaths

Timestamp:

02/11/22 11:18:52 (3 years ago)

Author:

robe

Comment:

--

PostGISExtensionPaths

@@ -92 +92 @@
 {{{
 :
-postgis--3.1MAX--3.3MAX.sql
-postgis--3.2MAX--3.3MAX.sql
-postgis--3.3MAX--3.3.0.sql
-postgis--3.3.0--3.3MAX.sql
+postgis--3.0.3--3.3.X.sql
+postgis--3.0.5--3.3.X.sql
+postgis--3.0.X--3.3.X.sql
+postgis--3.1.X--3.3.X.sql
+postgis--3.1.4--3.3.X.sql
+postgis--3.1.5--3.3.X.sql
+postgis--3.2.X--3.3.X.sql
+postgis--3.3.X--3.3.0.sql
 }}}
 ----
@@ -102 +106 @@
 1. We are staying between the lines. Respecting known practices, but still having much lighter weight scripts.
 2. A little less clutter, but we are relying on the user having the old version still installed so that they have a chain 
-postgis--<old-version-minor-micro>--<old-version-minor>MAX.sql
+postgis--<old-version-minor>MIN--<old-version-minor>MIN.sql
 3. An easier release cycle since extensions/updateable.mk doesn't need to list the prior micros.
 4. No change in upgrade extension workflow for packagers (or users who think of PostGIS as any other extension).