public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: tomjbe@gentoo.org
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [FRC] News item: Changing USE flags for >=app-backup/bacula
Date: Tue, 15 Aug 2017 11:33:57 +0200	[thread overview]
Message-ID: <150278963744.21353.3047478076045351690@ham.local.de> (raw)
In-Reply-To: <f804321a-e30d-1206-92d3-b134a1efda99@gentoo.org>

Quoting Kristian Fiskerstrand (2017-08-15 10:37:39)
> On 08/15/2017 12:29 AM, Rich Freeman wrote:
> > 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.
> 
> Can the "minimum"-use flag be utilized here?
>
Sounds reasonable and is worth thinking about. At least we could define the
meaning of "minimum" here in metadata.xml.

But, looking through portage there seems to be no "minimum" use flag anymore.
Seems it got dropped for some reasons.

Regards,

    Thomas



  reply	other threads:[~2017-08-15  9:34 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
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 [this message]
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=150278963744.21353.3047478076045351690@ham.local.de \
    --to=tomjbe@gentoo.org \
    --cc=gentoo-dev@lists.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