From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/2] distutils-r1.eclass: disable setuptools validation of pypi.org allowed strings
Date: Tue, 12 Nov 2024 15:00:28 -0500 [thread overview]
Message-ID: <eab9b11f-7eb1-4631-a53e-56a4435a7a55@gentoo.org> (raw)
In-Reply-To: <c499b3c5a19f5163d781c6d2b0edafd7c46b810d.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 861 bytes --]
On 11/12/24 1:37 PM, Michał Górny wrote:
>> diff --git a/eclass/distutils-r1.eclass b/eclass/distutils-r1.eclass
>> index 7ab8dcae3265..9b9ba4b803ac 100644
>> --- a/eclass/distutils-r1.eclass
>> +++ b/eclass/distutils-r1.eclass
>> @@ -1360,6 +1360,17 @@ distutils_pep517_install() {
>> EOF
>> )
>> fi
>> + if [[ ${BDEPEND} != *dev-python/trove-classifiers* ]]; then
>
> It's not valid to access stacked variables like BDEPEND from ebuilds.
For what reason is it invalid? Is it about whether this will work
correctly or is there a policy reason banning it or... ?
Note that this happens inside of a phase function, not at global scope.
So the value of the variable is determined by the contents of the
environment file, not from the incremental value when sourcing the
eclass at global scope.
--
Eli Schwartz
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2024-11-12 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 17:21 [gentoo-dev] [PATCH 1/2] distutils-r1.eclass: disable setuptools validation of pypi.org allowed strings Eli Schwartz
2024-11-12 17:21 ` [gentoo-dev] [PATCH 2/2] dev-python/setuptools: drop no longer necessary trove-classifiers workaround Eli Schwartz
2024-11-12 18:37 ` [gentoo-dev] [PATCH 1/2] distutils-r1.eclass: disable setuptools validation of pypi.org allowed strings Michał Górny
2024-11-12 20:00 ` Eli Schwartz [this message]
2024-11-12 20:09 ` Michał Górny
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=eab9b11f-7eb1-4631-a53e-56a4435a7a55@gentoo.org \
--to=eschwartz@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