hi guys, On Thu, 2006-11-23 at 12:30 +0100, David Gil wrote:
> Maybe I am completely wrong, but phpgacl does not need (mysql|
> postgresql)-client, dbconfig-common needs them (#353617).
>
> I am not happy to make phpgacl depends on (mysql|postgresql)-client
> since the package could be configured manually (not using dbconfig:
> there is a debconf question for this purpose).
>
> All packages using dbconfig-common are affected by this bug. I think
> it's better to improve dbconfig-common than adding more code and depends
> to all other packages.
there's an open bug on this for the dbconfig-common package, actually.
the tricky thing is we want to avoid depending on every supported
database client (it'd be annoying to have to install postgres
libs/clients for a mysql app and vice versa). but at the same time,
it's silly to offer to configure an application for mysql if the
mysql client isn't available.
there have been a few propsed solutions, but nothing substantial has
resulted from it yet. iirc, the general idea is that:
(a) the packages in question should still have (foo | bar) depends on
cmdline clients.
(b) in dbconfig-common, if the user selects an option for cmdline
clients that aren't installed, they're prompted with an error dialog,
the dbconfig-common hooks gracefully stop (or perhaps they're given a
choice to go back and choose another dbtype).
(c) if the admin later installs the required cmdline packages, they
should be able to dpkg-reconfigure the dbc-using package to use the new
dbtype as always.
sean
signature.asc
Description: This is a digitally signed message part
