| 1 |
2010-11-29 01:24:50 Alex Alexander napisał(a): |
| 2 |
> On 28 Nov 2010, at 22:20, Michał Górny <mgorny@g.o> wrote: |
| 3 |
> |
| 4 |
> > On Sun, 28 Nov 2010 20:32:16 +0100 |
| 5 |
> > Arfrever Frehtes Taifersar Arahesis <Arfrever@g.o> wrote: |
| 6 |
> > |
| 7 |
> >> PYTHON_DEPEND will be required. Otherwise each "${range_of_versions}" |
| 8 |
> >> should be included between "<<" and ">>" markers. |
| 9 |
> > |
| 10 |
> > Do we really need to introduce those ugly markers? AFAICS in all places |
| 11 |
> > they're used you could simply either use version numbers themselves or |
| 12 |
> > '*' (instead of '<<>>', and '*[...]' instead of '<<[...]>>'). |
| 13 |
> > |
| 14 |
> |
| 15 |
> I agree, reading these markers hurts my eyes :p |
| 16 |
|
| 17 |
Some markers are necessary. Read the following examples in an ebuild NOT supporting installation |
| 18 |
for multiple Python ABIs: |
| 19 |
|
| 20 |
# Dependency on Python 2 or 3 |
| 21 |
PYTHON_DEPEND="<<2 3>>" |
| 22 |
|
| 23 |
# Dependency on Python 2 and 3 |
| 24 |
PYTHON_DEPEND="<<2>> <<3>>" |
| 25 |
|
| 26 |
-- |
| 27 |
Arfrever Frehtes Taifersar Arahesis |
Archives