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

[Regina Obe]

In light of the fact we just seem to be going around in circles with this
one.

I'm going to mark this as a FAILE even the revised proposal of a 0-byte.,
And I'll just make adjustments to my windows packaging script.


> -----Original Message-----
> From: Regina Obe [mailto:lr at pcorp.us]
> Sent: Thursday, June 23, 2022 3:37 PM
> To: 'PostGIS Development Discussion' <postgis-devel at lists.osgeo.org>
> Subject: RE: [postgis-devel] PSC Vote: Get rid of micro in PostGIS
Extension
> scripts (and comments from others)
> 
> > > So how about this so we keep the ANY as final target:
> > >
> > > postgis--2.0.0--3.3.MAX.sql -> 0 byte file
> > > postgis--3.3.MAX--3.3.0.sql
> > > -> postgis--ANY-3.3.0.sql  (this can still be a
> > > symlink)
> > > it will still be fatter than just making any a 0 byte, but I can
> > > live with having two fat files on windows.
> >
> > How's this different from:
> >
> >   postgis--2.0.0--ANY.sql  (0 bytes)
> >   postgis--ANY-3.3.0.sql (the only upgrade script)
> >
> > --strk;
> [Regina Obe]
> Because we don't want
> 
> postgis--2.0.0--ANY.sql
> 
> as that gets overwritten with every single minor install.
> 
> Having a
> 
> postgis--2.0.0--3.3.MAX.sql
> 
> Will only get overwritten by micro upgrades which is acceptable.
>