[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Not depending on shlibs because of plugins?



Hi,

I'm packaging a database wrapper library (http://oss.devit.com/yada/).
Its purpose is to provide one single API to a program and let the user
configure if the database used is actually postgres/mysql/sqlite. The
actual interfacing with the databases is done by .so plugins that are
dlopened at run time.

Currently my package will depend on all of the database libs:

| Depends: [...], libmysqlclient15off (>= 5.0.24-2), libpq4 (>= 8.1.4), libsqlite3-0 (>= 3.3.8)

This kind of defeats the purpose of the package, the program(mer) uses
this library in order not to pull in any (or even all) specific
databases.

Is it in this case ok if I replace ',' by '|' there? This would allow
the user to really choose what database backend he wants.

The alternative solution would be to put the plugins into separate
packages and then depend on libyada-mysql | libyada-postgres |
libyada-sqlite. As these packages would merely contain a single file,
that seems bloat to me.

Comments?

Christoph
-- 
cb@df7cb.de | http://www.df7cb.de/

Attachment: signature.asc
Description: Digital signature


Reply to: