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>
Subject: Re: [gentoo-dev] [FRC] News item: Changing USE flags for >=app-backup/bacula
Date: Tue, 15 Aug 2017 08:21:20 -0400	[thread overview]
Message-ID: <CAGfcS_n48L+ahjkmBsf8x+LWEjmgmmYreFKaqf2OK8KZw6wOZg@mail.gmail.com> (raw)
In-Reply-To: <55d4128b-8def-c341-cb9a-20775303bec5@gentoo.org>

On Tue, Aug 15, 2017 at 5:45 AM, Kristian Fiskerstrand <k_f@gentoo.org> wrote:
> On 08/15/2017 11:33 AM, tomjbe@gentoo.org wrote:
>> 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.
>>
>
> typo; "minimal"...

The meaning of the minimal flag varies considerably throughout the
tree.  It is common only because its meaning morphs from package to
package.

For example, could you say that a client-only install that still
installs the X11 components is "minimal?"

-- 
Rich


  reply	other threads:[~2017-08-15 12:21 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
2017-08-15  9:45         ` Kristian Fiskerstrand
2017-08-15 12:21           ` Rich Freeman [this message]
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_n48L+ahjkmBsf8x+LWEjmgmmYreFKaqf2OK8KZw6wOZg@mail.gmail.com \
    --to=rich0@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