[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 14:04:42 UTC 2016

On 25.07.2016 15:54, Carsten Leonhardt wrote:

>> 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?
> Yes. Only what really has to be different would be in database-specific
> packages. This also shuts up the lintian warnings about conflicting
> dbgsym-packages :-)

We then have to be careful with the unpack ordering for the packages,
because the directord and stored have to be (re)started after the
database-specific packages have been configured or otherwise they could
end up being started too soon.

This is why in the current packages contain a manual inserted
invoke-rc.d call in prerm/postinst inside bacula-director-DBTYPE while
the init-script itself is in bacula-director-common.

To be able to just use plain debhelper and remove this manual kludge is
why I moved the init-script and systemd service to the
bacula-director-DBTYPE package in the first place.


-------------- 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/4fdbeb1a/attachment-0001.sig>

More information about the pkg-bacula-devel mailing list