On 15/12/10 12:06, justin wrote: > Hi, > > after testing this, and I have to say it mostly works smooth and fine, I > hit a huge problem. > > I wanted to emerge a package which just depends on glibc provided libs > for the oposite ABI my main ABI is. This specific package has an > optional support for python which would require to have a second python > installation, so I disabled it. Nevertheless the package inherits the > python.eclass which DEPENDS on eselect-python, which DEPENDS on python. > Resulting in the need of a two ABI python installation although I don't > want python support. > > To solve this there are two options: > > 1. Eclasses shouldn't be allowed to depend unconditionally on packages. > In case of python where there is PYTHON_DEPEND="python? X" it should be > doable. > 2. USE dependend inherit of eclasses > > > justin >
Please ignore this, I found somewhere deeply buried in a DEP the python dependency. It wasn't from the eclass Sorry for the noise.
signature.asc
Description: OpenPGP digital signature
