era eriksson <[EMAIL PROTECTED]> writes: > In <http://bugs.debian.org/296461>, you write: > > In order to upgrade from a previous twiki installation, the > > upstream script UpgradeTwiki is quite [useful]. > > If you are using a Debian package, you should not be updating things > in place. dpkg will be rightfully upset if you change an installed > package behind its back. Upgrade to a new version of the Debian > package (perhaps a locally created backport?), or install directly > from upstream sources, and don't use the Debian package in the first > place. > > Granted, it would be interesting to see how well the upgrade script > would be at upgrading the source of a Debian package ... Perhaps > that's actually what you are suggesting? > > /* era */ >
Hmmm... I suggest you have a look at what UpgradeTwiki does ;) It's about upgrading the data (i.e. the standard set of pages, the preferences, the templates, all kind of stuff that twiki uses in order to work well, beyond the scripts). Ok, it ay e used to upgrade the bin/ and lib/ directories too, but that's not the point... debconf won't help upgrading the data : that's where it lacks some tool. The scripts are upgraded by denconf : perfect. But unless you upgrade the data, they may no longer work as expected. That's where UpgradeTwiki comes to the rescue. But anyways, this will require a human intervention at all cases... and a bit of understanding of a diff/merge tool. Hope this is a bit more clear this time. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) APRIL (http://www.april.org) - Vive python (http://www.python.org) Pétition contre les brevets logiciels : http://petition.eurolinux.org
