[gentoo-dev] Re: Getting EAPI 5 *use.stable.mask to work in gx86?

[Duncan <1i5t5.duncan@cox.net>]

Michał Górny posted on Fri, 14 Dec 2012 16:15:05 +0100 as excerpted:

> On Fri, 14 Dec 2012 15:08:24 +0000 Markos Chandras <hwoarang@gentoo.org>
> wrote:
> 
>> > I'd like to point out that my proposal implies that the *current*
>> > arches become the stable arches, and new sub-arches would be the
>> > testing ones. Therefore, everyone will be allowed to touch like
>> > everyone is allowed to touch the *stable* profiles today.
>> >
>> > In other words, we mask python_targets_pypy* in the base profiles,
>> > and unmask them in the testing sub-profiles for amd64 & x86.
>> 
>> I fear that the stable and testing profiles will diverge way too much
>> as time passes. But if you feel that maintainers and herds will be able
>> to keep the 'diff' between them as minimum as possible, then I have no
>> objections.
> 
> Well, my hope is that we will be able to do it mostly via a common
> 'testing' profile (or per-arch testing profiles) which will be parents
> to other sub-profiles.

Yes.  Divergence over time is a worry, but we've had cascading profiles 
for quite some time now, so in theory, all that would be needed here is a 
a set of cascading "testing" profiles that simply inherit the stable 
profiles.  Then the testing profiles can simply inherit the stable 
profiles, with the only difference being the new EAPI-5 files in the 
testing profiles (and perhaps eventually the deprecation and in a year or 
two the final removal of the old profiles, with everything from them then 
moved to the new ones).

As long as that's KEPT the only difference...

-- 
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