Ciaran McCreesh <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Fri, 28 Dec 2007 12:28:10 +0000:
> On Fri, 28 Dec 2007 13:25:13 +0100 > "Santiago M. Mola" <[EMAIL PROTECTED]> wrote: >> On Dec 28, 2007 1:03 PM, Ciaran McCreesh >> <[EMAIL PROTECTED]> wrote: >> > There's no particular reason that new version formats can't be >> > introduced in a new EAPI so long as the version strings don't appear >> > in ebuilds using older EAPIs or in profiles. Ditto for naming rules. >> >> Errr... so should we use new files in profiles for such new formats? >> (for example, p.masking an ebuild with a new version format). > > Possibly. Currently there's simply no way of doing it, nor of using > non-EAPI-0 features anywhere in profiles (you can't, for example, use > slot deps in package.mask). Requesting clarification of a point, here: I understand the ban on non-EAPI-0 features in in-tree profiles, since users could be using old PMs, but it's fine using them in /etc/portage/*, provided one has upgraded to an appropriately compatible PM, correct? I ask because based on the kde overlay documentation, I have a lot of entries like this in /etc/portage/package.keywords: # kde4 overlay kde-base kde-base/kdelibs:kde-svn ** -- 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 -- [EMAIL PROTECTED] mailing list
