From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org, pr@gentoo.org
Subject: Re: [gentoo-dev] [FRC] News item: Changing USE flags for >=app-backup/bacula
Date: Mon, 14 Aug 2017 23:55:20 +0200 [thread overview]
Message-ID: <1502747720.9741.0.camel@gentoo.org> (raw)
In-Reply-To: <20170814215842.55855987@ham>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
On pon, 2017-08-14 at 21:58 +0200, Thomas Beierlein wrote:
> 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'
This is still negative logic in disguise. clientonly = noserver.
> * '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.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 988 bytes --]
next prev parent reply other threads:[~2017-08-14 21:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 19:58 [gentoo-dev] [FRC] News item: Changing USE flags for >=app-backup/bacula Thomas Beierlein
2017-08-14 21:55 ` Michał Górny [this message]
2017-08-14 22:29 ` Rich Freeman
2017-08-15 4:55 ` tomjbe
2017-08-15 6:43 ` Michał Górny
2017-08-15 9:19 ` tomjbe
2017-08-15 12:16 ` Rich Freeman
2017-08-15 17:49 ` tomjbe
2017-08-16 1:32 ` M. J. Everitt
2017-08-16 1:45 ` [gentoo-dev] " Duncan
2017-08-16 6:04 ` tomjbe
2017-08-15 8:37 ` [gentoo-dev] " Kristian Fiskerstrand
2017-08-15 9:33 ` tomjbe
2017-08-15 9:45 ` Kristian Fiskerstrand
2017-08-15 12:21 ` Rich Freeman
2017-08-15 13:25 ` Kristian Fiskerstrand
2017-08-15 14:02 ` Rich Freeman
2017-08-16 12:36 ` tomjbe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1502747720.9741.0.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox