On Wed, Nov 22, 2006 at 01:57:53PM +0100, Steinar H. Gunderson wrote: > Shouldn't this code rather reside in dbconfig-common?
I don't know... I haven't investigated what dbconfig-common does if you relies on the default configuration of available database backends. I would hope that ones that can't be fullfilled are automatically skipped by default. This package (and as it seems, many others) explicitly tells dbconfig-common that it wants both the options mysql and pgsql backends (excluding the sqlite backend) as choices. I'm not sure that having dbconfig-common ignoring the explicit advice given from the package is always the best idea. OTOH, I don't know why this package discriminates sqlite. Maybe most packages shouldn't be passing explicit backend options at all... -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
