-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[EMAIL PROTECTED] wrote:
| Hi
|
| do you think such a configuration layer should depends on every
| database interface ?
|
| Wouldn't it be cleaner to have the package using dbconfig depends
| on the database it can work with and have test in dbconfig to
| only show option regarding installed databases (or databases
| detectable via the already installed db client pacakges ?

It will be a better solution. But in this moment dbconfig-common *use*
one of them mysql-client or postgresql-client, the other aplication
could not need it.

Policy says:

"Every package must specify the dependency information about other
packages that are required for the first to work correctly."

If there no one of postgresql-client and mysql-client, it fails to work
in all case, then it has to depend on (at least) one of them. But
unfortunately, it doesn't solve the problem of the other package.

A possible solution could be if there exists virtual packages
dbconfig-mysql-common and dbconfig-postgres-common that depends on
(mysql or postgres) and dbconfig-common.

| PS: sorry if the style is a bit rude. I am always working on
| improving my english skills but debian comes first :)

me too... :)
- --
e-mail: Miguel Gea Milvaques <debian(@nospam)miguelgea.com>
Blog: http://www.livejournal.com/users/xerakko/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCRcRANTNQylgICMQRAmtUAJ0cbLiz3Grud86ZYtZaTPMUNoL9fQCgonKd
sVU5IVAlbedBuKJV2qjOeyM=
=YtgM
-----END PGP SIGNATURE-----


-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to