| 1 |
On Monday 11 of January 2010 01:25:45 Arfrever Frehtes Taifersar Arahesis |
| 2 |
wrote: |
| 3 |
> 2010-01-10 21:56:01 Fabian Groffen napisa³(a): |
| 4 |
> > On 10-01-2010 09:29:28 +0100, Arfrever Frehtes Taifersar Arahesis wrote: |
| 5 |
> > > I would like to suggest introduction of support for PYTHON_DEPEND |
| 6 |
> > > variable, which would be a better replacement for NEED_PYTHON |
| 7 |
> > > variable. NEED_PYTHON variable does not allow to specify that e.g. |
| 8 |
> > > only versions of Python 2 are accepted. (Eventually PYTHON_DEPEND |
| 9 |
> > > variable will have to be set only in ebuilds of packages not |
| 10 |
> > > supporting installation for multiple versions of Python.) |
| 11 |
> > |
| 12 |
> > Can you explain the intended use of this variable, and why normal DEPEND |
| 13 |
> > is not sufficient? |
| 14 |
> |
| 15 |
> PYTHON_DEPEND is intented to simplify specification of dependency on |
| 16 |
> Python. |
| 17 |
> |
| 18 |
> PYTHON_DEPEND="2:2.5" is shorter than: |
| 19 |
> DEPEND="|| ( =dev-lang/python-2.7* =dev-lang/python-2.6* |
| 20 |
> =dev-lang/python-2.5* )" |
| 21 |
|
| 22 |
Doesn't that accidentally mean that dev-lang/python is improperly slotted and |
| 23 |
all 2.x releases should be slotted with :2? |
| 24 |
So that dependency string would look like: |
| 25 |
DEPEND=">=dev-lang/python-2.5.0:2" |
| 26 |
|
| 27 |
-- |
| 28 |
regards |
| 29 |
MM |
Archives