From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] implicit RDEPEND
Date: Mon, 7 Aug 2006 19:25:37 -0400 [thread overview]
Message-ID: <200608071925.38197.vapier@gentoo.org> (raw)
In-Reply-To: <200608071936.53307.carlo@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
prev parent reply other threads:[~2006-08-07 23:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 14:12 [gentoo-dev] autotools.eclass and binary packages Christian Heim
2006-08-05 18:37 ` Mike Frysinger
2006-08-05 19:32 ` Zac Medico
2006-08-05 20:08 ` Mike Frysinger
2006-08-05 21:29 ` Zac Medico
2006-08-05 22:26 ` [gentoo-dev] implicit RDEPEND Mike Frysinger
2006-08-06 0:02 ` Zac Medico
2006-08-07 17:36 ` Carsten Lohrke
2006-08-07 23:25 ` Mike Frysinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608071925.38197.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox