| 1 |
Fabian Groffen posted on Mon, 11 Jan 2010 08:50:30 +0100 as excerpted: |
| 2 |
|
| 3 |
> On 11-01-2010 01:25:45 +0100, Arfrever Frehtes Taifersar Arahesis wrote: |
| 4 |
>> > Can you explain the intended use of this variable, and why normal |
| 5 |
>> > DEPEND is not sufficient? |
| 6 |
>> |
| 7 |
>> PYTHON_DEPEND is intented to simplify specification of dependency on |
| 8 |
>> Python. |
| 9 |
>> |
| 10 |
>> PYTHON_DEPEND="2:2.5" is shorter than: DEPEND="|| ( |
| 11 |
>> =dev-lang/python-2.7* =dev-lang/python-2.6* =dev-lang/python-2.5* )" |
| 12 |
> |
| 13 |
> So if there is enough space to express the dependency with the current |
| 14 |
> syntax, is it worth introducing a new shorthand for it then? |
| 15 |
> |
| 16 |
> Also for this example, why does 2:2.5 expand to 2.7, 2.6 and 2.5? I |
| 17 |
> would have expected 2.0 ... 2.5. Maybe the language isn't as intuitive |
| 18 |
> then as Sebastian pointed out. |
| 19 |
|
| 20 |
Initially intuitive, perhaps not, but reasonably easy after reading the |
| 21 |
explanation: |
| 22 |
|
| 23 |
The first position is major python version, the second if present, |
| 24 |
minimal version (within that major), so it can be read as =>version, the |
| 25 |
third if present, maximum version (within that major), so it can be read |
| 26 |
as <=. |
| 27 |
|
| 28 |
Thus, the above "2:2.5" means major version 2, minimal version 2.5 (no |
| 29 |
maximum version within that major), so 2.5+. |
| 30 |
|
| 31 |
-- |
| 32 |
Duncan - List replies preferred. No HTML msgs. |
| 33 |
"Every nonfree program has a lord, a master -- |
| 34 |
and if you use the program, he is your master." Richard Stallman |
Archives