1 |
2010-11-28 21:20:31 Michał Górny napisał(a): |
2 |
> On Sun, 28 Nov 2010 20:32:16 +0100 |
3 |
> Arfrever Frehtes Taifersar Arahesis <Arfrever@g.o> wrote: |
4 |
> |
5 |
> > PYTHON_DEPEND will be required. Otherwise each "${range_of_versions}" |
6 |
> > should be included between "<<" and ">>" markers. |
7 |
> |
8 |
> Do we really need to introduce those ugly markers? AFAICS in all places |
9 |
> they're used you could simply either use version numbers themselves or |
10 |
> '*' (instead of '<<>>', and '*[...]' instead of '<<[...]>>'). |
11 |
|
12 |
I prefer to use a character sequence, which isn't valid in DEPEND/RDEPEND/PDEPEND. |
13 |
|
14 |
I don't know what you mean by "version numbers". Remember that each "<<>>" in an ebuild with empty |
15 |
RESTRICT_PYTHON_ABIS is replaced in DEPEND/RDEPEND by: |
16 |
python_abis_2.4? ( dev-lang/python:2.4 ) |
17 |
python_abis_2.5? ( dev-lang/python:2.5 ) |
18 |
python_abis_2.6? ( dev-lang/python:2.6 ) |
19 |
python_abis_2.7? ( dev-lang/python:2.7 ) |
20 |
python_abis_3.0? ( dev-lang/python:3.0 ) |
21 |
python_abis_3.1? ( dev-lang/python:3.1 ) |
22 |
python_abis_3.2? ( dev-lang/python:3.2 ) |
23 |
python_abis_2.5-jython? ( dev-java/jython:2.5 ) |
24 |
|
25 |
-- |
26 |
Arfrever Frehtes Taifersar Arahesis |