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 - The . isn't legal as the first character in a flag name. (Paludis has been using [.foo=bar] and the like in user eapi contexts to allow fancy queries on metadata. It would be a shame to have to change that syntax just for some hypothetical possible use of . in use flag names that looks really really weird anyway.) > I'm planning to use e.g. REQUIRED_USE, which isn't available in EAPI <4. Or in EAPI 4 for that matter, going by the current state of GLEPs and PMS... -- Ciaran McCreesh
signature.asc
Description: PGP signature
