On Monday 07 August 2006 13:36, Carsten Lohrke wrote: > 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.
i prefer to make the common behavior the default ... if more packages than not
will simply be doing:
RDEPEND="${DEPEND}"
then typing that up a zillion times is a waste
> > - 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(), ...
you're looking at it wrong, what you need is not broken by my suggestion
[ebuild
set some vars to affect eclass
(eclass env sets up *DEPEND and saves them to $ECLASS_*DEPEND)
ebuild env sets up *DEPEND and saves them to *DEPEND]
-mike
pgpUERpqSuNuC.pgp
Description: PGP signature
