[pkg-bacula-devel] [pkg-bacula-commits] [bacula] 02/04: Move bscan into it's own package, making bacula-sd-DBTYPE obsolete
leo at debian.org
Sun Jul 24 16:08:17 UTC 2016
>> Move bscan into it's own package, making bacula-sd-DBTYPE obsolete
> Isn't bscan database dependent? The bscan I have on my system links to
> libmysqlclient.so and I guess the Postgres one links to the appropriate
> postgrey library.
> Having only one package with bscan will not work then, won't it?
hm, but the binary is exactly the same in all packages. It links to
libbaccats, which is a link to libbaccats-DBTYPE, which then links to
I'm thinking of re-introducing a bacula-director package in the same
way, which then depends on bacula-director-DBTYPE. That also solves the
init conflict in a clean way.
More information about the pkg-bacula-devel