On Sun, 2 Apr 2006 12:09:52 -0400 sean finney <sean...@debian.org> wrote: > having finally found some time to sit down and think about this > problem in more detail, i think i have a solution that will > make most people happy: > > - during installation (config script), dbconfig-common will examine > the list of supported database types vs the installed cmdline tools.
The annoying problem with this is that it is very well possible that the required command-line client is installed together with the package. As the configuration can be done before the packages are unpacked, the to-be installed command-line client will go unnoticed. So I am not yet convinced that this is the proper fix. An ugly (half?) hack would be to defer configuration for multi-db package to postinst time. > - if the intersection of these sets is empty, the admin will be prompted > with a notice telling them what programs/packages are required, and > dbconfig-common will exit gracefully. the package will install as if > they had opted out of assistance, but if reconfigured later and the > programs exist, they will have the choice to install as if it were a > new installation. Implementation wise it is probably more logical to just call the default error logic. > - if the intersection is non-empty, but different than the full list of > supported types, the admin will be prompted with a similar message, > but they will be given the choice to continue with the intersection > of supported types. Implementation wise it is probably easier to reuse the current selection question and state that there may be more options. So just treat the intersection as supported types. Paul
signature.asc
Description: OpenPGP digital signature
