Re: [gentoo-project] Introducing an optional files directory in the Portage tree with an embedded install condition and individual maintainers. (was Re: [gentoo-project] Proposal for add-on file utility (run after emerge update))

[Rich Freeman]

On Sun, Jun 16, 2013 at 3:22 PM, Tom Wijsman <TomWij@g.o> wrote:
> Either by denoting USE flags in USE as special _or_ introducing a
> separate OUSE variable.
>
> They don't have to be "openrc", "cron", "systemd" but could be like
> "init-scripts", "cron-files", "systemd-units"; to not collide with any
> existing USE flags, if any.
>
> Do they start to depend on each other? Why?

Bottom line is that in order to accomplish any of this we need to
expand PMS to specify a syntax, implement this stuff in portage, and
then start modifying all our ebuilds so that heaven-forbid you don't
get an openrc script installed if you don't set USE=openrc.

I don't think any of this is worth it for a one block text file.

This is really one of those situations where any decision is better
than no decision.  The general consensus so far is that stuff like
this just gets installed and users/devs who don't like it can use
INSTALL_MASK.  I could care less whether we do it that way or via USE
flags, but it seems like we'll still be debating this when I retire.

If people are going to quit over this, then I suspect that we're just
going to have to deal with the inevitable - if 4 people are willing to
quit over the INSTALL_MASK approach then I'm sure as many will quit
over just about any approach...

Rich