Re: [gentoo-project] Council meeting: Tuesday 14 August 2012, 19:00 UTC

[Zac Medico <zmedico@gentoo.org>]

On 08/14/2012 03:21 PM, Andreas K. Huettel wrote:
> Am Dienstag, 14. August 2012, 23:55:47 schrieb Zac Medico:
>> It seems like there's some confusion here. Approving a new EAPI and
>> deciding to use a new EAPI in a given profile are two entirely different
>> things. If we want to us a new EAPI in a profile, we just have to deploy
>> it such that users are only exposed to that profile when they
>> consciously running `eselect profile` (and they can always revert back
>> to the previous profile if it turns out that their installed package
>> manager doesn't support the new profile).
> 
> Yeah but... either
> 1) we use such an obscure profile that noone actually notices the change, or
> 2) we try to change something in the "big, well-known profiles", 
> and then we're back at the start.
> 
> So what good is including a feature in a new profile if there is no way to 
> make it visible to "the users" in general?

You do it in all the new profiles, and deprecate the old profiles. Users
see the profile deprecation notice (or news item or other announcement)
and upgrade their profile.

> Also, in this particular case, "stable use masking" is useful because it makes 
> stabilization possible/simpler in cases where otherwise this would lead to 
> broken dependencies (stable depending on ~arch). If only one small sub-profile 
> provides the feature, we lose its whole advantage.

Yeah, that's why I'm saying to do it in *all* new profiles and deprecate
the old ones.
-- 
Thanks,
Zac