2010-10-25 16:03:01 Ciaran McCreesh napisał(a): > On Mon, 25 Oct 2010 15:56:18 +0200 > Arfrever Frehtes Taifersar Arahesis <[email protected]> wrote: > > 2010-10-25 15:42:00 Ciaran McCreesh napisał(a): > > > On Mon, 25 Oct 2010 15:24:23 +0200 > > > Arfrever Frehtes Taifersar Arahesis <[email protected]> wrote: > > > > 1. Support for "." characters in names of USE flags > > > > > > If you do this, you'll have to either convert everything using > > > Python ABIs to EAPI 4 immediately, or have two sets of flag names. > > > Won't users get confused if they have to set both python_abis_3_2 > > > (for EAPI < 4 packages) and python_abis_3.2 (for EAPI 4 packages)? > > > > There won't be any such USE flags for EAPI <4. > > Ok, that answers that objection. In that case I'd not be opposed to . > being allowed *provided*: > > - Portage explicitly enforces it not being allowed anywhere else, > including in profiles that aren't marked as eapi 4
I have implemented validation of syntax of USE flags in files in profiles: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commitdiff;h=9e9c822aae0c3daab208175025b161d6d34877fe -- Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
