From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Rust in Linux / linux-libre
Date: Tue, 20 Apr 2021 21:22:09 -0400 [thread overview]
Message-ID: <YH9+QfCpSZ811VUe@jasmine.lan> (raw)
We should continue working to improve Rust in Guix, because it won't be
too long before it's part of Linux, which linux-libre is downstream
from.
Problems I see now:
1) Rust isn't yet supported on all CPU architectures supported in Guix
2) Rust packages don't use the normal Guix dependency mechanism, leading
to a sub-standard developer experience
3) Bootstrapping Rust within Guix takes several days at least, again
leading to a sub-standard developer experience
I think that "developer experience" is important because it basically
determines how many people will be willing to help.
Here's a recent article on the subject from Linux Weekly News:
"Rust heads into the kernel?"
https://lwn.net/SubscriberLink/853423/8ed876f0d4a6dcb5/
reply other threads:[~2021-04-21 1:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YH9+QfCpSZ811VUe@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.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.
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).