Hi Sean, Thanks for your response.
On Mon, 2006-02-20 at 01:15 -0500, sean finney wrote: > if you depend on dbconfig-common, then you also need to depend on > the cmdline tools for the database types you support. otherwise > you'd have to install postgres clients and libraries even if you > were packaging a mysql app and vice versa. It still seems strange for my package to have to depend on a package that doesn't provide anything I directly use. I guess how I would like dbconfig-common to work would be to present a list of possible databases to install to (being the intersection between those that are available on the system and those that the package maintainer has provided schemas, etc for). The mysql, postgres and in the future (sqlite, etc) tools could be promoted to Recommended for dbconfig and then dbconfig would simply present options for those databases the admin has indicated they might want to use by installing the tools. Do you think there would be any chance of dbconfig-common moving to a scheme such as this in the future. Shall I downgrade this bug to a wishlist? Cheers -- Matt Brown [EMAIL PROTECTED] Mob +64 21 611 544 www.mattb.net.nz
signature.asc
Description: This is a digitally signed message part
