public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH 0/3] python*-r1.eclass: dev-lang/pypy use
Date: Mon, 21 Oct 2024 19:53:25 +0200	[thread overview]
Message-ID: <20241021175655.1377755-1-mgorny@gentoo.org> (raw)

Hello,

Here's a series of patches to update the eclasses for dev-lang/pypy dep.
Or to put it more precisely, a bugfix for `python_gen_any_dep()`
with USE dependencies, removal of dead code and then the dependency
change.

As noted in the commit message, dev-python/pypy3 will need to remain
around at least for some time after the next subslot bump so that users
get everything rebuilt with the new dep.

This also requires pkgcheck update.  The relevant changes have been
merged already, so pending the release + stabilization + infra upgrade
cycle.  This should also gives us enough time to test the new package
layout a bit before we commit to it finally (currently the system can
gracefully switch back on revert).



Michał Górny (3):
  python-any-r1.eclass: Fix python_gen_any_dep w/ PYTHON_REQ_USE
  python-any-r1.eclass: Remove obsolete variable
  python-utils-r1.eclass: Depend on dev-lang/pypy directly

 eclass/python-any-r1.eclass     | 5 ++---
 eclass/python-utils-r1.eclass   | 9 ++-------
 eclass/tests/python-utils-r1.sh | 4 +++-
 3 files changed, 7 insertions(+), 11 deletions(-)

-- 
2.47.0



             reply	other threads:[~2024-10-21 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 17:53 Michał Górny [this message]
2024-10-21 17:53 ` [gentoo-dev] [PATCH 1/3] python-any-r1.eclass: Fix python_gen_any_dep w/ PYTHON_REQ_USE Michał Górny
2024-10-21 17:53 ` [gentoo-dev] [PATCH 2/3] python-any-r1.eclass: Remove obsolete variable Michał Górny
2024-10-21 17:53 ` [gentoo-dev] [PATCH 3/3] python-utils-r1.eclass: Depend on dev-lang/pypy directly 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=20241021175655.1377755-1-mgorny@gentoo.org \
    --to=mgorny@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