On Sunday 06 August 2006 00:26, Mike Frysinger wrote:
> and i'm on the opposite side where implicit RDEPEND should be clean:

Why? I for one consider explicit dependencies much more clean. If Portage at 
some point should distinct between dependencies defined in ebuilds and 
eclasses, we'd need a defined way to set eclass dependencies in ebuilds, so 
Portage actually can do the distiction, not breaking the tree. 

> - eclass and ebuilds have their own sets of DEPEND/RDEPEND which do not in
> any way affect each other

That's not true. We use and need the functionality to set dependencies in the 
ebuild which take effect in the eclass. Be it by setting a variable before 
inherit or by an eclass function called from within the ebuild - need-kde(), 
need-apache(), ...

We can't source the eclass and have all its dependencies.


Carsten