public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: PR team <pr@gentoo.org>
Subject: Re: [gentoo-dev] [FRC] News item: Changing USE flags for >=app-backup/bacula
Date: Mon, 14 Aug 2017 18:29:19 -0400	[thread overview]
Message-ID: <CAGfcS_m_cz7XmDznE7+knts+Vy5qeEFtx+EkdXEv7mm_AzX1Xw@mail.gmail.com> (raw)
In-Reply-To: <1502747720.9741.0.camel@gentoo.org>

On Mon, Aug 14, 2017 at 5:55 PM, Michał Górny <mgorny@gentoo.org> wrote:
> On pon, 2017-08-14 at 21:58 +0200, Thomas Beierlein wrote:
>>
>> * '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.
>>

++

I guess to make it a bit more explicit, would it make sense to have 3 flags:

client - install the client   (or consider calling it file-daemon instead)
director - install the director
storage-daemon - install the storage daemon

Omit the first if we always want the client.  I don't see the need for
a "clientonly" flag if each of the two server components already have
their own flags.  If somebody doesn't want to have to know what each
of the components do they probably shouldn't be messing around with
Bacula as it is anything but install-and-forget.

-- 
Rich


  reply	other threads:[~2017-08-14 22:29 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
2017-08-14 22:29   ` Rich Freeman [this message]
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=CAGfcS_m_cz7XmDznE7+knts+Vy5qeEFtx+EkdXEv7mm_AzX1Xw@mail.gmail.com \
    --to=rich0@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