| 1 |
On Tue, 20 Mar 2012 20:35:17 +0100 |
| 2 |
Arfrever Frehtes Taifersar Arahesis <arfrever@g.o> wrote: |
| 3 |
|
| 4 |
> 2012-03-20 17:53:56 Michał Górny napisał(a): |
| 5 |
> > On Tue, 20 Mar 2012 17:41:39 +0100 |
| 6 |
> > Arfrever Frehtes Taifersar Arahesis <arfrever@g.o> wrote: |
| 7 |
> > |
| 8 |
> > > 2012-03-20 05:29:20 Luca Barbato napisał(a): |
| 9 |
> > > > Hi, I tried to avoid depending on eselect-python if the useflag |
| 10 |
> > > > is disabled. |
| 11 |
> > > > |
| 12 |
> > > > Please test and review. |
| 13 |
> > > |
| 14 |
> > > The proper fix is to make python.eclass add dependency on |
| 15 |
> > > app-admin/eselect-python only when ${CATEGORY}/${PN} is |
| 16 |
> > > dev-lang/python, dev-java/jython or dev-python/pypy. See bug |
| 17 |
> > > #341037. |
| 18 |
> > |
| 19 |
> > Couldn't we just push that dependency to the specific ebuilds? |
| 20 |
> |
| 21 |
> We want to control required version (>=20091230 in case of |
| 22 |
> app-admin/eselect-python) in 1 place. |
| 23 |
> |
| 24 |
|
| 25 |
this can be achieved by setting a variable that said ebuilds will append |
| 26 |
to (R)DEPEND; no need for complex 'if then else' on CAT/PN in an eclass |
| 27 |
for this. |
Archives