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