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