On Sat, Jun 07, 2008 at 05:33:54PM +0200, Pierre Habouzit wrote:
> > 3. We need to prepare a migration framework that uses the trick
> > I shown in the report.
> > Thanks strk for a past discussion about that :-)
> > That should allow a more soft migration in some cases, but anyway
> > Postgis REQUIRES running soft/hard upgrades scripts for all
> > its databases, and that is a MUST and users are warned about
> > that in README.Debian since ages. There's not a silver bullet.
> Well I was under the impression in the bug log that it also needed to
> keep an old version of a library during the upgrade wich is at best
> sloppy. If that's not needed, then yes, important works for me.
The resons for that is that the db contains a reference to library
used for building it. If one would maintain the db without running
the upgrade script, keeping the past libraries around is a way
to do that. That would not protect against uncompatible
changes in the postgis schema anyway. So that trick helps but
it's a partial solution (and for sure not elegant, a dirty trick as I said).
> Note that you have another RC bugopen that is quite trivial to fix on
> its own. We try to release, please keep your packages clean.
The other bug is fixed by yesterday upload.
Francesco P. Lovergine
Pkg-grass-devel mailing list