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