Re: Removing dbconfig support ?

2010-12-08 Thread sean finney
hi there,

(for future reference dbconfig-common-de...@lists.alioth.debian.org is
probably the proper place for this type of discussion).

On Mon, Dec 06, 2010 at 11:31:22AM +0100, Pierre Chifflier wrote:
 Since the package is using dbconfig since a few versions, I'm now facing
 an upgrade problem before I can upload 0.78.1.
 For the moment, I'm thinking about removing dbconfig-common support and
 let all the configuration happen in the PHP scripts but I can't tell the
 consequences on previous installations.
 What is the best (not problematic) solution ? Any idea / help will be
 appreciated.

one alternative i would suggest exploring is keeping dbconfig-common for
the database/database-user creation (and maybe initial SQL bootstrap),
and leave the upgrade task to the application if the app provides
better support for that.  for example, this is what is done in the
cacti package, which also has some fairly complicated/robust upgrade
tasks between versions.



sean



signature.asc
Description: Digital signature


Removing dbconfig support ?

2010-12-06 Thread Pierre Chifflier
Hi,

I'm maintaining a PHP-MySQL application (GLPI) which is currently using
dbconfig to create and upgrade the database.

However, this cause problems during upgrades since upstream does only
provide PHP scripts for upgrades, which are quite complicated. I have
been trying to maintain a conversion to SQL commands for upgrade, but
this is getting impossible for recent versions since some commands
involve changes on existing data and are cannot be done with SQL (this
had been confirmed by upstream, and does not seems to be possible to
change easily according to him).

Since the package is using dbconfig since a few versions, I'm now facing
an upgrade problem before I can upload 0.78.1.
For the moment, I'm thinking about removing dbconfig-common support and
let all the configuration happen in the PHP scripts but I can't tell the
consequences on previous installations.
What is the best (not problematic) solution ? Any idea / help will be
appreciated.

Thanks,
Pierre


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cfcbb7a.4070...@debian.org