public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Wegener <swegener@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] No automatic RDEPEND=DEPEND for ebuild and eclass anymore
Date: Thu, 7 Jul 2005 01:40:53 +0200	[thread overview]
Message-ID: <20050706234052.GF20687@lightning.stealer.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]

Hi all!

OK, subject isn't fully the truth. Portage doesn't set RDEPEND=DEPEND
for eclasses. So, please check your eclasses and if they only set DEPEND
and you need the RDEPEND=DEPEND thing, go ahead and add it to the
eclass!

For the ebuild part the plan is to remove the automatic RDEPEND=DEPEND
setting from portage. I can hear you scream:

- "But that's a nice feature!"
- "It makes my life easier. Don't do it!"

Here are the reasons for removing it:

- RDEPEND is the only variable that gets this special treatment. Less
  confusion, if we remove the "magic" from RDEPEND.
- The ebuild should clearly say what it needs and not rely on portage
  deciding the RDEPEND=DEPEND bit.
- Developers are just setting DEPEND and leave RDEPEND alone, which
  results in unnecessary RDEPENDs. The removal will (hopefully) make
  developers pay more attention and result in cleaner dependencies.
- eclasses don't have the automatic RDEPEND=DEPEND thing, the change
  will streamline ebuilds and eclasses to be treated equally.

Cheers,
Sven

-- 
Sven Wegener
Gentoo Developer
http://www.gentoo.org/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-07-06 23:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 23:40 Sven Wegener [this message]
2005-07-08 12:07 ` [gentoo-dev] No automatic RDEPEND=DEPEND for ebuild and eclass anymore Dan Armak
2005-07-08 13:08   ` Sven Wegener

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=20050706234052.GF20687@lightning.stealer.net \
    --to=swegener@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