From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: "Lazy" use flags?
Date: Fri, 12 Feb 2016 05:56:05 +0000 (UTC) [thread overview]
Message-ID: <pan$cdff7$205dc827$c2a4c9c9$6146da2f@cox.net> (raw)
In-Reply-To: CAGfcS_ma6-K=T2jyVZuY+G67FHgbqZ0QnJpgteGd_hhdgh+1-Q@mail.gmail.com
Rich Freeman posted on Thu, 11 Feb 2016 07:55:52 -0500 as excerpted:
> Now, auto-unmask could still propose sticking USE=+foo in your
> package.use if you have USE=-foo in your make.conf, which is already the
> behavior today. If you've made any explicit USE setting in your
> configuration, portage would never ignore it, but only suggest that you
> change it.
So my USE="-* ..." (without letting portage do autounmasking) would
continue to work just like it does now, correct?
Because I allow neither profile USE flags nor profile @system packages
(all such profile entries and package-based default-use are negated),
here, and my package.use files contain only specific exceptions to my
global USE policy settings, together with (generally date-stamped)
comments justifying exactly why that exception is there.
By definition, then, If I haven't specifically set USE=flag, my system
policy is USE=-flag, and I want to know about and specifically setup any
exceptions (or if justified change my system policy), so I can set the
justification notes at the same time.
Because I'd be rather put out at anyone suggesting that I have to
specifically -flag each individual flag I want to be hard off, not
squishy off, as that's all the flags I've not specifically set hard on.
--
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:[~2016-02-12 5:56 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 12:27 [gentoo-dev] "Lazy" use flags? Kent Fredric
2016-02-09 13:14 ` Daniel Campbell
2016-02-09 13:19 ` Kent Fredric
2016-02-09 13:22 ` Daniel Campbell
2016-02-09 13:28 ` Kent Fredric
2016-02-09 20:35 ` Róbert Čerňanský
2016-02-09 23:30 ` Tim Harder
2016-02-10 0:20 ` Kent Fredric
2016-02-10 1:12 ` Rich Freeman
2016-02-10 2:23 ` Kent Fredric
2016-02-10 20:00 ` Róbert Čerňanský
2016-02-11 0:18 ` Raymond Jennings
2016-02-11 0:42 ` Rich Freeman
2016-02-11 2:18 ` Kent Fredric
2016-02-11 2:51 ` Rich Freeman
2016-02-11 3:46 ` Daniel Campbell
2016-02-11 12:59 ` Rich Freeman
2016-02-11 13:54 ` NP-Hardass
2016-02-11 14:25 ` Kent Fredric
2016-02-11 23:51 ` Daniel Campbell
2016-02-11 4:57 ` Kent Fredric
2016-02-11 5:47 ` Raymond Jennings
2016-02-11 12:55 ` Rich Freeman
2016-02-11 14:19 ` M. J. Everitt
2016-02-11 14:32 ` Kent Fredric
2016-02-11 14:43 ` M. J. Everitt
2016-02-11 14:46 ` Kent Fredric
2016-02-11 14:48 ` M. J. Everitt
2016-02-11 14:53 ` Kent Fredric
2016-02-11 19:37 ` Róbert Čerňanský
2016-02-12 5:56 ` Duncan [this message]
2016-02-12 6:36 ` [gentoo-dev] " Kent Fredric
2016-02-12 11:26 ` Rich Freeman
2016-02-12 15:58 ` Gordon Pettey
2016-02-11 2:31 ` [gentoo-dev] " Kent Fredric
2016-02-10 3:08 ` Gordon Pettey
2016-02-10 3:29 ` Daniel Campbell
2016-02-12 0:01 ` William Hubbs
2016-02-12 0:12 ` Daniel Campbell
2016-02-12 1:23 ` Rich Freeman
2016-02-12 1:26 ` Daniel Campbell
2016-02-12 1:39 ` Rich Freeman
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$cdff7$205dc827$c2a4c9c9$6146da2f@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