From: "Matt Jolly" <kangie@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/rust-patches:master commit in: /
Date: Sat, 31 May 2025 05:53:09 +0000 (UTC) [thread overview]
Message-ID: <1748670728.2f5f9d1a670ddbfb09193750b7d6fefa24bfd2f4.kangie@gentoo> (raw)
Message-ID: <20250531055309.fuDsl0NWTysHtlLJQHpPaaGW0DcJsSq5YfhXm4BZ0R0@z> (raw)
commit: 2f5f9d1a670ddbfb09193750b7d6fefa24bfd2f4
Author: Matt Jolly <kangie <AT> gentoo <DOT> org>
AuthorDate: Sat May 31 05:52:08 2025 +0000
Commit: Matt Jolly <kangie <AT> gentoo <DOT> org>
CommitDate: Sat May 31 05:52:08 2025 +0000
URL: https://gitweb.gentoo.org/proj/rust-patches.git/commit/?id=2f5f9d1a
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-05-31 5:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 5:53 Matt Jolly [this message]
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.75 commit in: / Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.77 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.76 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.80 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.79 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.78 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.81 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.82 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.83 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.84 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.85 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.86 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:1.87 " Matt Jolly
2025-05-31 5:53 ` [gentoo-commits] proj/rust-patches:master " Matt Jolly
-- strict thread matches above, loose matches on Subject: below --
2025-05-31 5:53 [gentoo-commits] proj/rust-patches:1.74 " Matt Jolly
2025-05-31 5:55 Matt Jolly
2025-05-31 5:55 Matt Jolly
2025-06-02 9:25 Matt Jolly
2025-06-02 9:25 Matt Jolly
2025-06-02 9:48 Matt Jolly
2025-06-02 9:48 Matt Jolly
2025-06-03 4:33 Matt Jolly
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
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=1748670728.2f5f9d1a670ddbfb09193750b7d6fefa24bfd2f4.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