From: "Matt Jolly" <kangie@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/rust-patches:1.83 commit in: /
Date: Mon, 02 Jun 2025 09:25:15 +0000 (UTC) [thread overview]
Message-ID: <1748856136.7cf432eff81656ac286c1ff3e4d549f35c22c784.kangie@gentoo> (raw)
Message-ID: <20250602092515.aT4aM6B6coLCDUuqy0zWo6BpjxmQEDLXekoBtBcMPls@z> (raw)
commit: 7cf432eff81656ac286c1ff3e4d549f35c22c784
Author: Matt Jolly <kangie <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 2 09:22:16 2025 +0000
Commit: Matt Jolly <kangie <AT> gentoo <DOT> org>
CommitDate: Mon Jun 2 09:22:16 2025 +0000
URL: https://gitweb.gentoo.org/proj/rust-patches.git/commit/?id=7cf432ef
Initial commit with README
Signed-off-by: Matt Jolly <kangie <AT> gentoo.org>
README.rst | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/README.rst b/README.rst
new file mode 100644
index 0000000..9999e72
--- /dev/null
+++ b/README.rst
@@ -0,0 +1,24 @@
+###################
+Gentoo Rust Patches
+###################
+
+This repository contains patches required to build Rust on Gentoo Linux. These patches were previously
+part of the main Gentoo repository but have been moved here due to their size and to make maintenance easier.
+
+The patches are applied to the Rust source code during the build process. They address various issues such as
+compatibility with the Gentoo environment, specific compiler flags, and other adjustments needed for a successful build,
+or are backports to fix specific issues.
+
+Usage
+=====
+
+A branch will be created for each new Rust release (e.g. ``1.88``), and patches will be added to that branch as needed.
+
+Tags for ``${PV}`` will be created for each release, e.g. ``1.88.0``, ``1.88.1``, etc., to track the specific versions of
+Rust that these patches apply to. Revbumps will be tagged as required - if a patch is added or updated, a tag will be
+created for the new version (e.g. ``1.88.0-r1``).
+
+``master`` will contain patches required for ``nightly`` (live / ``9999``) ebuilds and will be updated as needed.
+
+To use the patches, you can clone this repository and apply the patches to the Rust source code before building
+(or use the Gentoo ebuild system which will handle this automatically!).
next reply other threads:[~2025-06-02 9:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 9:25 Matt Jolly [this message]
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.75 commit in: / Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.76 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.78 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.77 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.79 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.80 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.81 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.82 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.83 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.84 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.85 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.86 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.87 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:1.88 " Matt Jolly
2025-06-02 9:25 ` [gentoo-commits] proj/rust-patches:master " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.76.0-r101 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.75.0-r101 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.74.1-r101 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.77.1-r101 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.79.0-r101 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.78.0-r101 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.80.1-r101 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.81.0-r101 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.83.0-r3 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.82.0-r103 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.84.0-r2 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.84.1-r2 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.85.0-r2 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.85.1-r1 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.86.0-r2 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.87.0-r1 " Matt Jolly
2025-06-02 9:34 ` [gentoo-commits] proj/rust-patches:1.88.0_beta20250526 " Matt Jolly
-- strict thread matches above, loose matches on Subject: below --
2025-06-03 4:33 [gentoo-commits] proj/rust-patches:1.75 " Matt Jolly
2025-06-03 4:33 ` [gentoo-commits] proj/rust-patches:1.74 " Matt Jolly
2025-06-03 4:33 Matt Jolly
2025-06-02 9:48 Matt Jolly
2025-06-02 9:48 Matt Jolly
2025-06-02 9:25 Matt Jolly
2025-05-31 5:55 Matt Jolly
2025-05-31 5:55 Matt Jolly
2025-05-31 5:53 Matt Jolly
2025-05-31 5:53 Matt Jolly
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=1748856136.7cf432eff81656ac286c1ff3e4d549f35c22c784.kangie@gentoo \
--to=kangie@gentoo.org \
--cc=gentoo-commits@lists.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