[gentoo-dev] [FRC] News item: Changing USE flags for >=app-backup/bacula

[Thomas Beierlein <tomjbe@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 371 bytes --]

Bacula ebuilds uses some weird USE flags with mostly negative
logic ('do not build ..') coming from their build system.

With the actual major release (bacula-9.0.3) we should try to switch to
something more sane. I picked up the new flags from app-backup/bareos as
both ebuilds have a common anchestry.

Please comment on the proposed news item. 

Thanks,
	Thomas


-- 

[-- Attachment #2: 2017-08-14-bacula-changed-use-flags.en.txt --]
[-- Type: text/plain, Size: 1031 bytes --]

Title: Changing USE flags for >=app-backup/bacula-9.0.3
Author: Thomas Beierlein <tomjbe@gentoo.org>
Content-Type: text/plain
Posted: 2017-08-14
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <app-backup/bacula-9.0.3

Until now Bacula ebuilds uses the following set of USE flags:

* 'bacula-nodir' and 'bacula-nosd' are inhibiting installation of the 
  backup director and backup storage daemon respectively, 
* 'bacula-clientonly' drops all components but the file daemon.

Due to the negative logic of that flags the correct meaning is sometimes
difficult to grasp. Starting with version bacula-9.0.3 these USE flags will be
changed as follows:

* 'bacula-clientonly' becomes 'clientonly'
* 'bacula-nodir' will be replaced by 'director' but with inverted logic 
* 'bacula-nosd' will be replaced by 'storage-daemon' (also inverted).

'director' and 'storage-daemon' will be active by default resulting in an
installation with backup director and storage daemon enabled.

Please adapt your USE flag settings accordingly.