| 1 |
On 02/06/2010 03:03 AM, Arfrever Frehtes Taifersar Arahesis wrote: |
| 2 |
> 2010-02-05 17:40:00 Arfrever Frehtes Taifersar Arahesis napisał(a): |
| 3 |
>> - Dependency on Python 2 should be set correctly. You can specify it directly in |
| 4 |
>> {,R}DEPEND or use PYTHON_DEPEND. |
| 5 |
>> |
| 6 |
>> Example: |
| 7 |
>> PYTHON_DEPEND="2" |
| 8 |
>> |
| 9 |
>> inherit python |
| 10 |
> |
| 11 |
> It might be useful to provide another example: |
| 12 |
> If given package requires e.g. Python >=2.6, but does not support Python 3, then you can |
| 13 |
> set PYTHON_DEPEND="2:2.6". |
| 14 |
|
| 15 |
I noticed that this generates a depedency like "|| ( |
| 16 |
=dev-lang/python-2.7* =dev-lang/python-2.6* )" which is very similar |
| 17 |
to the way that QT3VERSIONS works in qt3.eclass. One thing that is |
| 18 |
sub-optimal about these types of dependencies is that you end up |
| 19 |
with lots of installed packages that have out-dated dependencies |
| 20 |
when the next minor version of python is released (python-2.8 in |
| 21 |
this case). In the case of the python dependencies, it might be more |
| 22 |
optimal to use a version range like ">=dev-lang/python-2.6 |
| 23 |
<dev-lang/python-3". |
| 24 |
|
| 25 |
-- |
| 26 |
Thanks, |
| 27 |
Zac |
Archives