multiple database support with dbconfig-common : metapackages ?

[Jérémy Lal <kapouer@melix.org>]

Hi,
i'm working on redmine package, which supports three db types :
sqlite, mysql, pgsql
and is using dbconfig-common to setup the db.

Instead of depending on :
sqlite3 | postgresql-client | mysql-client,
libdbd-sqlite3-ruby | libdbd-pg-ruby | libdbd-mysql-ruby
as bugzilla, drupal, and others do, which i think is
confusing the user; is it desirable to do as roundcube package, i.e.
providing three metapackages ? Each package providing the correct
dependencies for each db type.

Then it would give :
redmine depends on redmine-mysql | redmine-pgsql | redmine-sqlite

On second thought, one would like to have these metapackages :
for a php app:
- dbconfig-php-mysql | dbconfig-php-pgsql | dbconfig-php-sqlite
for a ruby app:
- dbconfig-ruby-mysql | dbconfig-ruby-pgsql | dbconfig-ruby-sqlite
and so on for other languages.
For example, dbconfig-ruby-pg would have these dependencies :
libdbd-pg-ruby, postgresql-client
Still, managing all the possibilities might create too much metapackages,
so it's probably better to stay with the first approach.

Thanks for any input on this.

Jérémy Lal