1 |
2010-02-06 13:14:41 Brian Harring napisał(a): |
2 |
> On Sat, Feb 06, 2010 at 12:03:11PM +0100, Arfrever Frehtes Taifersar Arahesis wrote: |
3 |
> > 2010-02-05 17:40:00 Arfrever Frehtes Taifersar Arahesis napisał(a): |
4 |
> > > - Dependency on Python 2 should be set correctly. You can specify it directly in |
5 |
> > > {,R}DEPEND or use PYTHON_DEPEND. |
6 |
> > > |
7 |
> > > Example: |
8 |
> > > PYTHON_DEPEND="2" |
9 |
> > > |
10 |
> > > inherit python |
11 |
> > |
12 |
> > It might be useful to provide another example: |
13 |
> > If given package requires e.g. Python >=2.6, but does not support Python 3, then you can |
14 |
> > set PYTHON_DEPEND="2:2.6". |
15 |
> |
16 |
> We really need better syntax than that. Particular reason you're |
17 |
> jamming py2k and py3k all into one? Breaking it down into |
18 |
> PYTHON2K_DEPEND and PYTHON3K_DEPEND |
19 |
|
20 |
There's no need for 2 variables when 1 variable is sufficient. |
21 |
|
22 |
> would involve lest magic in parsing |
23 |
|
24 |
At least I was able to exercise my bash skills and find a bug in bash :) . |
25 |
|
26 |
-- |
27 |
Arfrever Frehtes Taifersar Arahesis |