1 |
On Tue, Mar 20, 2012 at 5:05 PM, Alexis Ballier <aballier@g.o> wrote: |
2 |
> On Tue, 20 Mar 2012 17:57:29 -0300 |
3 |
> Alexis Ballier <aballier@g.o> wrote: |
4 |
> |
5 |
>> On Tue, 20 Mar 2012 20:35:17 +0100 |
6 |
>> Arfrever Frehtes Taifersar Arahesis <arfrever@g.o> wrote: |
7 |
>> |
8 |
>> > 2012-03-20 17:53:56 Michał Górny napisał(a): |
9 |
>> > > On Tue, 20 Mar 2012 17:41:39 +0100 |
10 |
>> > > Arfrever Frehtes Taifersar Arahesis <arfrever@g.o> wrote: |
11 |
>> > > |
12 |
>> > > > 2012-03-20 05:29:20 Luca Barbato napisał(a): |
13 |
>> > > > > Hi, I tried to avoid depending on eselect-python if the |
14 |
>> > > > > useflag is disabled. |
15 |
>> > > > > |
16 |
>> > > > > Please test and review. |
17 |
>> > > > |
18 |
>> > > > The proper fix is to make python.eclass add dependency on |
19 |
>> > > > app-admin/eselect-python only when ${CATEGORY}/${PN} is |
20 |
>> > > > dev-lang/python, dev-java/jython or dev-python/pypy. See bug |
21 |
>> > > > #341037. |
22 |
>> > > |
23 |
>> > > Couldn't we just push that dependency to the specific ebuilds? |
24 |
>> > |
25 |
>> > We want to control required version (>=20091230 in case of |
26 |
>> > app-admin/eselect-python) in 1 place. |
27 |
>> > |
28 |
>> |
29 |
>> this can be achieved by setting a variable that said ebuilds will |
30 |
>> append to (R)DEPEND; no need for complex 'if then else' on CAT/PN in |
31 |
>> an eclass for this. |
32 |
>> |
33 |
> |
34 |
> or also by adding a new python-implementation.eclass instead of |
35 |
> polluting an eclass used by hundreds of packages for only 3 special |
36 |
> ones... |
37 |
> |
38 |
|
39 |
A four-way if-then statement is not what I would call "complex". This |
40 |
was already present in the eclass anyway, so there is no additional |
41 |
"pollution". |
42 |
|
43 |
I have already committed Arfrever's patch. If anyone wants to move the |
44 |
dependency into the ebuilds, you are welcome to do so; patching the |
45 |
eclass was just faster/easier. |