[pkg-bacula-devel] [pkg-bacula-commits] [bacula] 02/04: Move bscan into it's own package, making bacula-sd-DBTYPE obsolete

Sven Hartge sven at svenhartge.de
Mon Jul 25 13:24:53 UTC 2016

On 25.07.2016 15:17, Carsten Leonhardt wrote:
>>> 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.
>> Did you mean "depending on bacula-common-DBTYPE"? Because
>> libaccats-DBTYPE.so is currently in that package.
> I mean this:
> bacula-director -> bacula-director-DBTYPE -> bacula-common-DBTYPE

I see. bacula-director-DBTYPE would then contain the documentation,
dbconfig-stuff and the make_catalog_backup scripts for each DBTYPE, correct?

The database specific library is in bacula-common-DBTYPE and used by the
director, the stored and bscan.

The init-script and service unit would then be in bacula-director, right?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/attachments/20160725/620e2467/attachment.sig>

More information about the pkg-bacula-devel mailing list