[postgis-devel] Extensions

[Paragon Corporation]

Sure.  I'll test on mine to see what is wrong or if it works on mine.  You
were testing with 9.1 right?

postgis_raster_upgrade_minor.sql

is a combination of postgis_upgrade_minor.sql, raster_upgrade_minor.sql

and some special logic needed for extensions to remove stuff  e.g. can't
have begin commit clauses
and if you drop something like a type have to remove from extension before
you can drop it.

though that doesn't explain why the various versions aren't being installed.

Thanks,
Regina

> -----Original Message-----
> From: pramsey at cleverelephant.ca 
> [mailto:pramsey at cleverelephant.ca] On Behalf Of Paul Ramsey
> Sent: Tuesday, January 10, 2012 4:58 PM
> To: PostGIS Development Discussion
> Cc: Paragon Corporation
> Subject: Extensions
> 
> Regina,
> I've added the extensions into the autoconf system, but there 
> are some subtleties and concerns.
> First the subtleties...
> 
> You'll note that
>   EXTVERSION    = @POSTGIS_LIB_VERSION@
> is the very obvious way the current version is brought into 
> the scripts.
> 
> If you look further down, you'll see a target named
>   sql_minor_upgrade
> and some fancy bash scripting. That creates all the micro 
> version targets up to the current micro version, and also 
> includes smarts so that if the current version is 
> 2.0.0alpha3, it generates micro version upgrades from 
> 2.0.0alpha1, and 2.0.0alpha2.
> 
> Now, looking at that target I got concerned that the only 
> input file was postgis_raster_upgrade_minor.sql so I changed 
> it to what I thought made sense, postgis_upgrade_minor.sql. 
> However I'm sure that's wrong in a different way.
> 
> I also note that when I run 'make all', I'm not seeing what I 
> expect as a minimum in the ./sql file, namely a 
> postgis--2.0.0.sql file, just a bare postgis.sql file. So it 
> seems there's other brings broke?
> Anyhow, the micro version generator and the version substitution work.
> To get in synch with your extension testing, we can set the 
> Version.config in trunk to 2.0.0alpha1 for now, and then 
> release it shortly once you think the extensions work. Yes?
> 
> p.
>