From: Nicolas Graves via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: guix-devel@gnu.org
Cc: maximedevos@telenet.be
Subject: rust-build-system from antioxidant
Date: Fri, 02 Jun 2023 20:02:50 +0200 [thread overview]
Message-ID: <87v8g5g2t1.fsf@ngraves.fr> (raw)
A few months ago, Maxime Devos worked on a new rust-build-system to
handle a few issues we were experiencing with cargo (see discussions on
antioxidant in guix-devel).
A month ago, we discussed about the possibility of the integration in
core guix, and the required steps. Maxime and I had a different
approach. Maxime highlighted the possibility to make a smooth transition
but once that would require many gradual changes and deprecation. My
approach was that since we'll have to eventually migrate all packages to
rust-build-system, and since we can freeze all former rust packages in
an archive channel, I would be clearer to make the transition at once.
Took me quite some time from there, but thanks to the huge work of
Maxime and a few rust patches, I've managed to compile ripgrep properly,
along with more than 350 packages which represent all transitive inputs
and native-inputs. It's basically a package-level copy of Maxime's work
on antioxidant, with more focus on "bootstrapping" properly (very few
packages are missing a test phase), and some work to cut down the number
of dependencies.
It's only a step, but a good one to continue the discussion about the
integration of this build-system (and the way it should be integrated).
You can find it in an archive right here for a 5 days (I would rather
not create a new 8 Gb repo online for 100 kb transferred, sorry).
https://drop.chapril.org/download/696f37be60f243fd/#-j9Nt_xiN9eUBCsHfMDHig
If we manage to continue this to reach 100% builds like the antioxidant
channel, we could indeed switch in one big commit. The workspace
build-system is not included yet.
--
Best regards,
Nicolas Graves
next reply other threads:[~2023-06-02 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 18:02 Nicolas Graves via Development of GNU Guix and the GNU System distribution. [this message]
2023-06-08 17:55 ` rust-build-system from antioxidant Maxime Devos
2023-06-12 1:17 ` Maxim Cournoyer
2023-06-12 10:10 ` Maxime Devos
2023-06-12 13:05 ` Maxim Cournoyer
2023-06-14 13:02 ` Maxime Devos
2023-07-02 20:12 ` Overruling and blocking Ludovic Courtès
2023-06-12 15:08 ` rust-build-system from antioxidant Vagrant Cascadian
2023-06-12 16:34 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-06-16 13:53 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-06-17 0:51 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8g5g2t1.fsf@ngraves.fr \
--to=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=ngraves@ngraves.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).