Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Fwd: [gentoo-dev-announce] Call for items for September 13 council meeting
Date: Fri, 16 Sep 2011 21:07:22
In Reply to: Re: [gentoo-dev] Fwd: [gentoo-dev-announce] Call for items for September 13 council meeting by Arfrever Frehtes Taifersar Arahesis
On 09/15/2011 05:20 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> 2011-09-16 01:54:44 Brian Harring napisał(a): >> On Fri, Sep 16, 2011 at 01:21:55AM +0200, Arfrever Frehtes Taifersar Arahesis wrote: >>> 2011-09-15 09:55:08 Ciaran McCreesh napisał(a): >>>> On Thu, 15 Sep 2011 09:35:21 +0200 >>>> Michał Górny <mgorny@g.o> wrote: >>>>> Could you point me to at least a single program not supporting dots >>>>> in useflags? My quick check shows that all PMs handle them well, quse >>>>> and euse as well. >>>> >>>> Hrm, it's rather disappointing that they're accepted everywhere. That >>>> really shouldn't happen... My excuse for Paludis is that I never quite >>>> got around to passing in additional flags to validation of names, and >>>> dots are legal in exheres-0 >>> >>> There is no reason for Gentoo to be worse than Exherbo and not allow dots in USE flags. >> >> Seriously Arfrever, drop the rhetoric here, and go fix the profile >> compatibility issue. > > I suggest to support files with "-${EAPI}" suffix. > Examples: > profiles/package.mask-5 > profiles/use.desc-5 > profiles/base/package.mask-5 > profiles/base/package.use-5 > profiles/base/package.use.force-5 > profiles/base/package.use.mask-5 > profiles/base/use.force-5 > profiles/base/use.mask-5 > profiles/desc/python_abis.desc-5 >
I'd prefer not to use separate files per eapi, since that effectively gives you multiple profiles that behave differently depending on the supported EAPI of the package manager. As an alternative, I suggest to use the 'eapi' file to specify the EAPI for all files in the directory. If you want to roll out EAPI 5 profiles sooner, then you can fork a new base profile that only supports EAPI 5 or later, and base new profiles off of that. Bumping the EAPI of the root profiles/eapi file would be a different matter, since it applies to the whole repository. If you want to version bump that repository-level EAPI, then you need to wait until at least 6 months after supporting package managers have been available in stable. -- Thanks, Zac