From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] Forced/automatic USE flag constraints (codename: ENFORCED_USE)
Date: Wed, 31 May 2017 12:38:31 +0000 (UTC) [thread overview]
Message-ID: <pan$10fd8$e8a2cde6$7f98564e$ffe5a0ce@cox.net> (raw)
In-Reply-To: 20170531093257.23b66f88@gentoo.org
Alexis Ballier posted on Wed, 31 May 2017 09:32:57 +0200 as excerpted:
>> For example:
>>
>> foo? ( bar )
>>
>> would mean 'if you have USE=foo, then USE=bar is enabled as well'. Not
>> 'find some random solution which satisfies this'. In other words, here
>> changing USE=foo into USE=-foo is not an acceptable solution.
>
>
> What if I specifically set USE=-bar in make.conf ? Do we really want PM
> to override that without telling me ?
Yes, override (tho the telling me bit would be up to the PM
implementation and could be as indirect as simply showing the new pulled-
in package in ask/pretend) because USE flags always control options and
don't disable mandatory requirements, which is what this scenario is
ultimately describing, even if it's /conditional/ mandatory.
If a user cares enough about not wanting whatever USE=bar pulls in,
they'll notice the pull-in in ask/pretend and abort the merge,
investigating and changing config or deciding they don't need that
package after all, just as they do with mandatory pull-ins now.
As for more direct indications, portage could and I'd expect would
indicate the USE override the same as it does for profile-masked and new-
version-deleted USE flags now, putting them in parentheses so the user
knows they no longer apply. I'm not familiar enough with other PMs to
know if/how they indicate such things, but I'd imagine they could
similarly treat it to the way they do masked flags today. After all,
it's simply another method of masking, only in this case it's dynamic, by
the PM at solve time.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-05-31 12:38 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 15:33 [gentoo-dev] [RFC] Forced/automatic USE flag constraints (codename: ENFORCED_USE) Michał Górny
2017-05-29 16:30 ` Kent Fredric
2017-05-29 16:44 ` Michał Górny
2017-05-29 18:00 ` Alexis Ballier
2017-05-29 21:23 ` Michał Górny
2017-05-29 21:31 ` Ciaran McCreesh
2017-05-29 22:01 ` Ulrich Mueller
2017-05-29 22:05 ` Ciaran McCreesh
2017-05-30 7:47 ` Alexis Ballier
2017-05-30 8:05 ` Ulrich Mueller
2017-05-30 8:10 ` Alexis Ballier
2017-05-30 7:42 ` Alexis Ballier
2017-05-30 8:22 ` Ciaran McCreesh
2017-05-30 8:46 ` Alexis Ballier
2017-05-30 8:56 ` Ciaran McCreesh
2017-05-30 9:25 ` Alexis Ballier
2017-05-30 12:00 ` Ulrich Mueller
2017-05-30 14:33 ` Michał Górny
2017-05-30 15:33 ` Alexis Ballier
2017-05-30 18:11 ` Michał Górny
2017-05-30 18:46 ` Alexis Ballier
2017-05-31 6:55 ` Michał Górny
2017-05-31 7:24 ` Ciaran McCreesh
2017-05-31 7:34 ` Alexis Ballier
2017-05-31 7:35 ` Michał Górny
2017-05-31 7:51 ` Ciaran McCreesh
2017-05-31 7:54 ` Alexis Ballier
2017-05-31 7:56 ` Alexis Ballier
2017-05-31 7:32 ` Alexis Ballier
2017-05-31 8:03 ` Michał Górny
2017-05-31 8:38 ` Alexis Ballier
2017-05-31 13:04 ` Michał Górny
2017-05-31 17:39 ` Alexis Ballier
2017-05-31 19:02 ` Michał Górny
2017-05-31 22:52 ` Ciaran McCreesh
2017-06-01 8:55 ` Alexis Ballier
2017-06-01 21:31 ` Michał Górny
2017-06-02 6:37 ` Michał Górny
2017-06-02 11:18 ` Alexis Ballier
2017-06-02 13:49 ` Michał Górny
2017-06-02 11:27 ` Alexis Ballier
2017-06-02 13:55 ` Michał Górny
2017-06-02 15:09 ` [gentoo-dev] " Martin Vaeth
2017-06-03 11:00 ` [gentoo-dev] " Alexis Ballier
2017-06-03 15:33 ` Michał Górny
2017-06-03 16:58 ` Alexis Ballier
2017-06-04 8:59 ` Alexis Ballier
2017-06-05 7:55 ` Alexis Ballier
2017-06-05 14:10 ` Michał Górny
2017-06-05 17:24 ` Alexis Ballier
2017-06-05 18:10 ` Michał Górny
2017-06-05 18:15 ` Ciaran McCreesh
2017-06-06 12:08 ` Alexis Ballier
2017-06-06 17:39 ` Michał Górny
2017-06-07 6:49 ` Michał Górny
2017-06-07 8:17 ` Alexis Ballier
2017-06-07 9:27 ` Michał Górny
2017-06-07 9:56 ` Alexis Ballier
2017-06-09 9:19 ` Michał Górny
2017-06-09 11:41 ` Alexis Ballier
2017-06-09 12:54 ` Michał Górny
2017-06-09 14:16 ` Alexis Ballier
2017-06-09 16:21 ` Michał Górny
2017-06-11 16:05 ` Alexis Ballier
2017-06-12 9:08 ` Alexis Ballier
2017-06-12 19:17 ` Michał Górny
2017-06-13 10:27 ` Alexis Ballier
2017-06-13 22:13 ` Michał Górny
2017-06-14 9:06 ` Alexis Ballier
2017-06-14 12:24 ` Michał Górny
2017-06-14 13:16 ` Alexis Ballier
2017-06-14 13:57 ` Michał Górny
2017-06-14 14:09 ` Alexis Ballier
2017-06-15 15:59 ` Michał Górny
2017-06-15 16:07 ` Alexis Ballier
2017-06-15 16:13 ` Ciaran McCreesh
2017-06-15 16:19 ` Alexis Ballier
2017-06-15 16:22 ` Ciaran McCreesh
2017-06-15 16:30 ` Alexis Ballier
2017-06-15 16:32 ` Ciaran McCreesh
2017-06-15 16:37 ` Alexis Ballier
2017-06-15 16:45 ` Ciaran McCreesh
2017-06-15 16:55 ` Alexis Ballier
2017-06-15 17:04 ` Ciaran McCreesh
2017-06-15 17:30 ` Alexis Ballier
2017-06-15 17:48 ` Ciaran McCreesh
2017-06-15 18:09 ` Alexis Ballier
2017-06-15 17:38 ` Michał Górny
2017-06-15 18:05 ` Alexis Ballier
2017-06-14 14:28 ` Alexis Ballier
2017-06-02 12:16 ` Alexis Ballier
2017-06-02 13:57 ` Michał Górny
2017-06-02 14:56 ` [gentoo-dev] " Martin Vaeth
2017-06-02 15:19 ` Ciaran McCreesh
2017-06-02 16:26 ` Martin Vaeth
2017-06-02 18:31 ` Martin Vaeth
2017-06-02 1:17 ` [gentoo-dev] " A. Wilcox
2017-06-02 1:28 ` Rich Freeman
2017-06-02 1:33 ` A. Wilcox
2017-06-02 5:08 ` Michał Górny
2017-05-31 12:38 ` Duncan [this message]
2017-05-30 21:13 ` Kent Fredric
2017-05-30 8:29 ` Michał Górny
2017-05-30 9:34 ` Alexis Ballier
2017-05-30 14:12 ` Michał Górny
2017-05-29 19:24 ` Ciaran McCreesh
2017-05-29 19:42 ` Michał Górny
2017-05-29 19:44 ` Ciaran McCreesh
2017-06-05 8:26 ` Alexis Ballier
2017-06-09 12:35 ` Jason A. Donenfeld
2017-06-09 12:42 ` Michał Górny
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='pan$10fd8$e8a2cde6$7f98564e$ffe5a0ce@cox.net' \
--to=1i5t5.duncan@cox.net \
--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