From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] implicit RDEPEND
Date: Sat, 05 Aug 2006 17:02:36 -0700 [thread overview]
Message-ID: <44D5319C.2030606@gentoo.org> (raw)
In-Reply-To: <200608051826.02842.vapier@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mike Frysinger wrote:
> On Saturday 05 August 2006 17:29, Zac Medico wrote:
>> I'm not satisfied with the current implicit RDEPEND behavior either. I
>> propose that we make repoman force explicit definition of RDEPEND.
>
> and i'm on the opposite side where implicit RDEPEND should be clean:
> - eclass and ebuilds have their own sets of DEPEND/RDEPEND which do not in any
> way affect each other
> - RDEPEND, if not set, is defined as $DEPEND
That change is more difficult to do because your talking about changing the implicit behavior for all eclasses and all ebuilds. It seems like it would require an EAPI bump if we want to ensure a smooth migration path that is free of wild fluctuations in RDEPEND. If we take that step, we need to be absolutely sure that we *really* love having implicit RDEPEND="${DEPEND}" at all levels (for both eclasses and ebuilds).
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE1TGW/ejvha5XGaMRAiYWAJ9KxCtfllC5Pl47milHR0x+9liUawCfUWEJ
EZVpT4FAYCl2679I+em/zQU=
=Eqpo
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-06 0:06 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 [this message]
2006-08-07 17:36 ` Carsten Lohrke
2006-08-07 23:25 ` Mike Frysinger
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=44D5319C.2030606@gentoo.org \
--to=zmedico@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