Changes between Version 11 and Version 12 of PostGISExtensionPaths
- Timestamp:
- Feb 11, 2022, 11:18:52 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PostGISExtensionPaths
v11 v12 92 92 {{{ 93 93 : 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 94 postgis--3.0.3--3.3.X.sql 95 postgis--3.0.5--3.3.X.sql 96 postgis--3.0.X--3.3.X.sql 97 postgis--3.1.X--3.3.X.sql 98 postgis--3.1.4--3.3.X.sql 99 postgis--3.1.5--3.3.X.sql 100 postgis--3.2.X--3.3.X.sql 101 postgis--3.3.X--3.3.0.sql 98 102 }}} 99 103 ---- … … 102 106 1. We are staying between the lines. Respecting known practices, but still having much lighter weight scripts. 103 107 2. 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.sql108 postgis--<old-version-minor>MIN--<old-version-minor>MIN.sql 105 109 3. An easier release cycle since extensions/updateable.mk doesn't need to list the prior micros. 106 110 4. No change in upgrade extension workflow for packagers (or users who think of PostGIS as any other extension).