From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Kent Fredric <kentnl@gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Disable --autounmask auto-unmasking keywords / masks by default
Date: Thu, 10 Oct 2019 01:09:43 -0700 [thread overview]
Message-ID: <7b4bf9a0-ee8f-a5a0-d29b-0a7c7c02bdcd@gentoo.org> (raw)
In-Reply-To: <20191010155705.2bf1479b@katipo2.lan>
[-- Attachment #1.1: Type: text/plain, Size: 851 bytes --]
On 10/9/19 7:57 PM, Kent Fredric wrote:
> On Wed, 9 Oct 2019 19:45:34 -0700
> Zac Medico <zmedico@gentoo.org> wrote:
>
>> I'd prefer to disable --autounmask by default and include warnings about
>> harmful behavior in the documentation.
>
> I think autounmasks behaviour with regards to USE flags is useful,
> (heh), its just everything else it does tends to violate stability
> assumptions.
>
> For instance, I can see why automatically escalating "arch" to "~arch"
> may be useful in some cases, but its a very dangerous default,
> *especially* for perl.
We can add --autounmask-use=<y|n> option that's enabled by default when
--autounmask is unspecified.
When --autounmask=y is specified, we'll have full autounmask behavior.
When --autounmask=n is specified, we'll have --autounmask-use=n behavior.
--
Thanks,
Zac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
prev parent reply other threads:[~2019-10-10 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 23:53 [gentoo-dev] [RFC] Disable --autounmask auto-unmasking keywords / masks by default Kent Fredric
2019-10-10 2:45 ` Zac Medico
2019-10-10 2:57 ` Kent Fredric
2019-10-10 3:35 ` Michael Everitt
2019-10-10 3:39 ` Kent Fredric
2019-10-10 8:09 ` Zac Medico [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=7b4bf9a0-ee8f-a5a0-d29b-0a7c7c02bdcd@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kentnl@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