From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: storing predefined INSTALL_MASK directory lists in repos
Date: Sat, 11 Jan 2014 19:59:38 +0100 [thread overview]
Message-ID: <20140111185938.8636.qmail@stuge.se> (raw)
In-Reply-To: <pan$59502$7af8ab9d$4106e1e9$2d4a917a@cox.net>
Duncan wrote:
> >> INSTALL_MASK="systemd bash-completion"
> >>
> >> What are your thoughts?
> >
> > It seems like this will generally duplicate all -USE flags.
> >
> > Would it make sense to instead have a single setting which changes the
> > meaning of USE to be that everything not USEd is install-masked?
>
> No, this would not be a duplicate.
I did generalize, but think more about this - certainly for both
Michał's examples I have already either set or unset "systemd" and
"bash-completion" in USE.
> Gentoo policy is that the mere installation of a few small and
> harmless if not used files should not be controlled by USE flags
Policy doesn't matter if they doesn't make sense. Maybe I am asking
if Michał's idea could be implemented by changing that policy.
An INSTALL_MASK setting in make.conf doesn't require recompile any
less than USE setting already do.
> install-mask is an existing general control mechanism fit for the task.
..
> So the next step in automation and safety is as proposed here, provide a
> standard location for pre-created "safe" mask files that a user can then
> choose to activate
..
> a less sharp and hazardous way of activating mask settings pre-cleared
> as "safe" by gentoo devs
The mechanism wouldn't change. I think this discussion is only about
having the most expressive knobs.
//Peter
next prev parent reply other threads:[~2014-01-11 18:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 10:20 [gentoo-dev] RFC: storing predefined INSTALL_MASK directory lists in repos Michał Górny
2014-01-11 11:53 ` Peter Stuge
2014-01-11 15:19 ` [gentoo-dev] " Duncan
2014-01-11 18:59 ` Peter Stuge [this message]
2014-01-13 20:39 ` Donnie Berkholz
2014-01-11 15:56 ` [gentoo-dev] " Luis Ressel
2014-01-11 16:01 ` Michał Górny
2014-01-11 16:15 ` Alan McKinnon
2014-01-11 16:52 ` Michał Górny
2014-01-11 17:11 ` Alan McKinnon
2014-01-11 17:28 ` Michał Górny
2014-01-11 16:21 ` Luis Ressel
2014-01-11 16:46 ` 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=20140111185938.8636.qmail@stuge.se \
--to=peter@stuge.se \
--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