How to handle this: mantis DB upgrade 0.19 -> 1.0.6
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there,
i'm currently packaging a new version of mantis as i just adopted the
package. But i'm stuck on the point, how to handle updates.
Its like this:
Mantis in Debian is v. 0.19. Current upstream is 1.0.6. There has been
huge changes in the database. I want to use dbconfig-common to handle
database installation and so forth, but i am unsure if it will handle
the situation and of what i need to do for it to do so. Upstream author
provides a php - script for updating, which works good and could be
called via php4-cli and a little "hack" which will give it the right
parameters. But is that really what i want? Is there a better way to do
it with dbconfig-common. And if no: Is there a way to wrap
dbconfig-common arround this "hack"?
Best Regards
Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD4DBQFFZwHvTKIzE6LY9r8RAk3sAKCCHDgLZAn7lLzxzS4iWzfe3meLzACYi5pt
Cz7MdHRxxOVYPn7EnHFEgw==
=j1F2
-----END PGP SIGNATURE-----
Reply to: