| 1 |
On 15/12/10 12:06, justin wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> after testing this, and I have to say it mostly works smooth and fine, I |
| 5 |
> hit a huge problem. |
| 6 |
> |
| 7 |
> I wanted to emerge a package which just depends on glibc provided libs |
| 8 |
> for the oposite ABI my main ABI is. This specific package has an |
| 9 |
> optional support for python which would require to have a second python |
| 10 |
> installation, so I disabled it. Nevertheless the package inherits the |
| 11 |
> python.eclass which DEPENDS on eselect-python, which DEPENDS on python. |
| 12 |
> Resulting in the need of a two ABI python installation although I don't |
| 13 |
> want python support. |
| 14 |
> |
| 15 |
> To solve this there are two options: |
| 16 |
> |
| 17 |
> 1. Eclasses shouldn't be allowed to depend unconditionally on packages. |
| 18 |
> In case of python where there is PYTHON_DEPEND="python? X" it should be |
| 19 |
> doable. |
| 20 |
> 2. USE dependend inherit of eclasses |
| 21 |
> |
| 22 |
> |
| 23 |
> justin |
| 24 |
> |
| 25 |
|
| 26 |
Please ignore this, I found somewhere deeply buried in a DEP the python |
| 27 |
dependency. It wasn't from the eclass |
| 28 |
|
| 29 |
Sorry for the noise. |
Archives