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/4] python eclasses: PyPy3.10 update + cargo LTO strip-flags
Date: Wed, 12 Jul 2023 14:22:51 +0200 [thread overview]
Message-ID: <20230712122503.309626-1-mgorny@gentoo.org> (raw)
Hi,
Here's a quick patchset on top of vimproved's patchset to remove
`--reflink=auto` calls from the eclasses. It does two things:
1. Update the eclass to assume PyPy3.10 (and therefore cease supporting
PyPy3.9 as a target).
2. Strip LTO flags when distutils-r1 is used with cargo.eclass.
The second commit is a bit hacky but I think it's a good enough approach
that doesn't require us to strip LTO unconditionally or add yet another
control variable to tell the eclass if we're dealing with Rust or not.
Michał Górny (4):
python-utils-r1.eclass: Require >=dev-python/pypy3-7.3.12
python-utils-r1.eclass: pypy3 is now 3.10-only
distutils-r1.eclass: Update addpredict for PyPy3.10
distutils-r1.eclass: Disable LTO when using cargo.eclass
eclass/distutils-r1.eclass | 9 ++++++++-
eclass/python-utils-r1.eclass | 7 +++----
2 files changed, 11 insertions(+), 5 deletions(-)
--
2.41.0
next reply other threads:[~2023-07-12 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 12:22 Michał Górny [this message]
2023-07-12 12:22 ` [gentoo-dev] [PATCH 1/4] python-utils-r1.eclass: Require >=dev-python/pypy3-7.3.12 Michał Górny
2023-07-12 12:22 ` [gentoo-dev] [PATCH 2/4] python-utils-r1.eclass: pypy3 is now 3.10-only Michał Górny
2023-07-12 12:22 ` [gentoo-dev] [PATCH 3/4] distutils-r1.eclass: Update addpredict for PyPy3.10 Michał Górny
2023-07-12 12:22 ` [gentoo-dev] [PATCH 4/4] distutils-r1.eclass: Disable LTO when using cargo.eclass Michał Górny
2023-07-12 17:42 ` Ulrich Mueller
2023-07-12 17:48 ` 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=20230712122503.309626-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