From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Guidelines for dangerous USE flags
Date: Tue, 22 Aug 2017 18:44:16 +0000 [thread overview]
Message-ID: <robbat2-20170822T184142-226085743Z@orbis-terrarum.net> (raw)
In-Reply-To: <17347fd7-d6ed-4c08-8d02-24df9237b576@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On Tue, Aug 22, 2017 at 01:22:51PM -0400, Michael Orlitzky wrote:
> 1) require EXTRA_ECONF to enable it.
> 2) hide it behind a masked USE flag.
>
> Both options require about the same amount of work from the user, namely
> editing something under /etc/portage. What do y'all think is the best
> way to proceed? Are there other examples in the tree I could follow?
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).
--
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]
next prev parent reply other threads:[~2017-08-22 18:44 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 ` Robin H. Johnson [this message]
2017-08-24 15:22 ` [gentoo-dev] " Michael Orlitzky
2017-08-25 22:07 ` William Hubbs
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=robbat2-20170822T184142-226085743Z@orbis-terrarum.net \
--to=robbat2@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