public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Guidelines for dangerous USE flags
Date: Fri, 25 Aug 2017 17:07:04 -0500	[thread overview]
Message-ID: <20170825220704.GA29025@linux1.home> (raw)
In-Reply-To: <7f59fb4d-e7a2-3bd1-9274-de0bc94affb8@gentoo.org>

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

On Thu, Aug 24, 2017 at 11:22:24AM -0400, Michael Orlitzky wrote:
> On 08/22/2017 02:44 PM, Robin H. Johnson wrote:
> > From a Gentoo Infrastructure team perspective, we'd strongly prefer USE
> > flags, because that fits better into existing configuration management
> > tools, almost none of which have handling for EXTRA_ECONF or rebuilding
> > after EXTRA_ECONF changes (rebuild-on-USE-change is supported).
> > 
> > And please do bring that option back, we do use it for NRPE in a limited
> > set of cases (eg to avoid hard-coding passwords into the NRPE config).
> > 
> 
> It's back, but the flag is masked. Since the USE flag mask is going to
> retroactively hit people who use --newuse, I suggest adding

I don't recommend masking it. If it is off by default, you can always
output a warning via ewarn if users enable it.

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2017-08-25 22:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 17:22 [gentoo-dev] Guidelines for dangerous USE flags Michael Orlitzky
2017-08-22 17:37 ` Sven Vermeulen
2017-08-24  3:06   ` [gentoo-dev] " Duncan
2017-08-29  9:21     ` Kent Fredric
2017-08-29 10:21       ` Duncan
2017-08-22 18:44 ` [gentoo-dev] " Robin H. Johnson
2017-08-24 15:22   ` Michael Orlitzky
2017-08-25 22:07     ` William Hubbs [this message]

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=20170825220704.GA29025@linux1.home \
    --to=williamh@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