From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bugzilla Bug 79337 make repoman complain if DEPEND and RDEPEND are not set.
Date: Mon, 30 May 2005 19:51:48 -0500 [thread overview]
Message-ID: <20050531005148.GB7265@exodus.wit.org> (raw)
In-Reply-To: <200505290232.45343.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Sun, May 29, 2005 at 02:32:45AM -0400, Mike Frysinger wrote:
> On Sunday 29 May 2005 01:48 am, Alec Warner wrote:
> > The actual fix to the bug is a minor one, a small check to Repoman to
> > make sure ebuilds have both DEPEND and RDEPEND set; and to warn if they
> > are not set.
> >
> > However the use of DEPEND and RDEPEND in the manner that they are
> > requesting is a large change and thus was brought here for discussion.
>
> i'm against this ... the current behavior is the logical default imho
What of eclasses? Bug 58819 comes to mind...
Ebuilds get the RDEPEND="${REPEND-${DEPEND}}" default, but
eclasses don't. Would rather there was a standard the whole way
through personally, even if eclasses are a bit more complex
in enforcing the RDEPEND="${RDEPEND-${DEPEND}}" behaviour. That
said, I'm not much for the auto-setting of RDEPEND :)
So... extend the ebuild behaviour to eclasses, or...
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-31 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 5:48 [gentoo-dev] Bugzilla Bug 79337 make repoman complain if DEPEND and RDEPEND are not set Alec Warner
2005-05-29 6:32 ` Mike Frysinger
2005-05-31 0:51 ` Brian Harring [this message]
2005-05-31 0:55 ` Mike Frysinger
2005-06-01 14:25 ` Jason Stubbs
2005-06-01 15:21 ` Georgi Georgiev
2005-06-01 15:32 ` Jason Stubbs
2005-06-01 16:37 ` Brian Harring
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=20050531005148.GB7265@exodus.wit.org \
--to=ferringb@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