[postgis-devel] Packaging 2.1

[Paragon Corporation]

I vaguely remember this being an issue with 1.5 when going from 1.4 to 1.5
that distros uninstalled 1.4 and strk fixed the issue. Can't find the ticket
but it was the version checking that was the problem.  I know now we have
raster as wel and maybe that uses the old model.

Have you tried upgrading without using extensions to see if that works.



In windows we just overlay (never blindly uninstall since some of us like to
run mutliple versions) and since the extension files already are versioned,
it doesn't affect 2.0 install aside from upgrading the GEOS, GDAL and proj.
The installers also are versioned -- meaning on stack builder you see 2.0
and will see 2.1 and see 1.5 for older versions.

However we do have the issue that since some files like GEOS and proj and
gdal are shared, when someone does an uninstall, we make sure not to remove
these files for fear of breaking a newer install which is a bit of a dirty
problem. It's dirty but at least not damaging.

 
We also try to keep the GEOS/Proj/GDAL versions the same across 2.0/2.1 to
prevent accidental upgrade difference in order from breaking the upper if
done out of order.

That said -- we haven't packaged installer for windows postgis 2.1 just have
the binaries http://postgis.net/windows_downloads (in unreleased section)
for those that are anxious.


.  We were going to wait till 9.3 comes out so we can suffer the pain in one
go :)

Thanks
Regina


-----Original Message-----
From: postgis-devel-bounces at lists.osgeo.org
[mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
Sent: Monday, August 26, 2013 6:59 PM
To: postgis-devel at lists.osgeo.org
Subject: [postgis-devel] Packaging 2.1

Hi all,
We've come across an issue that occurs when packaging 2.1. (In this case, in
a slackware package, but the issue will probably occur everywhere)
Basically, if you've made a "postgis2" package that says its version is 2.1
and that it supercedes the old 2.0 "postgis2" package what will happen is
that postgis-2.1.so will be installed, and postgis-2.0.so will be removed.
Then when you go to ALTER EXTENSION upgrade, the upgrade will fail, because
the old library (which functions are still bound to) is missing.
The only way things work is if a "postgis-2.0.so" file is still around. 
This seems like a big packaging problem.

First, on Windows question: does installing a new version of the windows
package just write in the new files, and leave the old files untouched? I'm
assuming "yes", otherwise you'd have seen the same problem.

Second, on Linux question: what should we do? We almost need to start fully
numbering our postgis packages to make it clear you can have multiple minor
versions installed simultaneously: postgis2.0, postgis2.1, etc. This will
make our package names even more awesomely awful, but I don't see a way
around it.

P.




--
Paul Ramsey
http://opengeo.org
http://postgis.net


_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel