[Dbconfig-common-devel] Re: Bug#398634: [phpgacl] alternative patch without hard dependencies on both db clients.

[sean finney]

hej andreas,

On Thu, 2006-11-23 at 19:33 +0100, Andreas Henriksson wrote:

> A slightly different way would be to:
> - have dbconfig-common depend on "sqlite | mysql-client |
> postgresql-client" to make sure atleast one of the supported clients is
> always installed.

unfortunately, this won't work because some apps work only with mysql,
others with mysql | pgsql, others sqlite only, thus it's possible that
unless it specified its own dependencies, the app would be installed
without any supported db clients installed. (phpmysqladmin on
a system with dbconfig+sqlite already installed, for example)

> - When package doesn't pass any $dbc_dbtypes to dbconfig-common, detect
> at runtime which clients are available when adding the default set of db
> clients, and offer only those as choices (and possibly mention what
> other choices could be available and how to install the required db
> client).
> - offer to safely abort, so additional db client can be installed, and
> then the user can restart the configuration by running "dpkg-reconfigure
> <package-that-uses-dbconfig-common>".

this part is more or less what i've suggested with things in a slightly
different order.  


	sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20061123/2280a8f2/attachment.pgp