On 02/02/2017 01:01 PM, Rich Freeman wrote:
> On Thu, Feb 2, 2017 at 11:25 AM, Michael Orlitzky <m...@gentoo.org> wrote:
>>
>> If (base == minimal), then all of the upstream defaults need to be added
>> to package.use for the upstream-defaults profile. That's bad,
> 
> I'll go further and say that it is unacceptably bad.
> 

Only if anyone wants an upstream-defaults profile. But nobody's asked
for one, in contrast with the large number of users who want minimal.


> Is there a better way we can have our cake and eat it too?  I'll admit
> that a huge package.use on the minimal profile isn't a whole lot
> better than a huge package.use on all the other profiles.

Every important upstream default is already enabled in some profile. If
dropping a particular IUSE default breaks desktop systems, then that
flag belongs enabled in the desktop profile. If it breaks every system,
then let's keep it default.


> Do we need another form of syntax in individual ebuilds to try to
> separate out the various cases you cite?  Does anybody care to
> actually suggest one?

Definitely not. I was hoping to simplify things, not complicate them. We
have a list of flags that can be enabled for each package. As a general
principle, it makes sense to either (a) disable them all by default, or
(b) enable them all by default. Having what is essentially a random
selection enabled by default for each package is chaos.


> I still think that we shouldn't encourage users to lightly deviate
> from all the upstream defaults. 

Deviating from upstream defaults is why we have USE flags in the first
place. No one really wants the upstream defaults, they want

  (nothing) + (what their profile provides) + (what they enable),

not least of all because that assumption is how they came up with the
list of flags in (what they enable) in the first place.

If dropping an IUSE default hurts some profile, then stick the default
in that profile. Nothing breaks, and it's not too much work, and we get
back to a sane system of profile inheritance rather than having every
ebuild and profile trying to XOR one another.


Reply via email to