public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nowa Ammerlaan <andrewammerlaan@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Serious problem with inheritance of RDEPEND, BDEPEND, DEPEND,
Date: Fri, 1 Nov 2024 19:36:57 +0100	[thread overview]
Message-ID: <0295fb8e-f85f-4e5d-947a-f6219c6fbda6@gentoo.org> (raw)
In-Reply-To: <e04472ef-116d-48a8-8975-cd551103ecc1@inode64.com>

On 01/11/2024 19:28, Desarrollos WEB wrote:
> 
> Seeing this problem, you should always use the variables RDEPEND, 
> BDEPEND, DEPEND, adding content, not replacing it (of course, there may 
> be a special case), but as a general rule you should add, not replace, 
> these variables, both in eclass and ebuilds.
> 

Please see chapter 10 of the PMS: 
https://dev.gentoo.org/~ulm/pms/head/pms.html#chapter-10

accumulate-vars The IUSE, REQUIRED_USE, DEPEND, BDEPEND, RDEPEND, 
PDEPEND and IDEPEND variables are handled specially when set by an 
eclass. They must be accumulated across eclasses, appending the value 
set by each eclass to the resulting value after the previous one is 
loaded. For EAPIs listed in table 10.1 as accumulating PROPERTIES and 
RESTRICT, the same is true for these variables. Then the eclass-defined 
value is appended to that defined by the ebuild. In the case of RDEPEND, 
this is done after the implicit RDEPEND rules in section 7.3.7 are applied.

Your issue is not what you think it is, looks to me like a missing 
BDEPEND on setuptools, please report it as a bug.





  reply	other threads:[~2024-11-01 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 18:28 [gentoo-dev] Serious problem with inheritance of RDEPEND, BDEPEND, DEPEND, Desarrollos WEB
2024-11-01 18:36 ` Nowa Ammerlaan [this message]
2024-11-01 18:57   ` Eli Schwartz

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=0295fb8e-f85f-4e5d-947a-f6219c6fbda6@gentoo.org \
    --to=andrewammerlaan@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