RE:RE:dbconfig-common upgrade strategy
> You're welcome! Maybe open a bug? ;)
Yes but it seems that dbconfig-common developpement stall :((
> Well, there might be a way to integrate this in your own postinst
> script, after configuring the database. *But* that you require some
> fiddling and usage of functions to load the configuration to check which
> database type is used.
In my case the database is necessary on the same machine.
I generate a .my.cnf file connected via socket during the packageinstallation.
Do you know if dbconfig-common generate this kind of connection information during the installation process ?
This way it should be possible to generate a better .my.cnf file which could work with a deported database server.
> But keep in mind: dbconfig-common is generic, your database can be
> anywhere, not just localhost.
> All you need is the mysql-client or postgresql-client and proper remote
> access to setup a database on somewhere else.
> It would require the admin to setup the database beforehand.
for now my package depends on mysql-server.
But it would be more flexible if I could depend only on mysql-client.
> Internals of dbconfig-common are a bit weird sometimes, e.g. preseeding
> to disable the database setup will require a special setting in debconf
> (/internal/skip-preseed), so that the install choices (dbconfig-install)
> are used from debconf instead of loading default first.
Yes this piec of software is a bit ackward.
Cheers
Fred
Reply to: