From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: rustfmt-1.5.1
Date: Sun, 26 Mar 2023 17:31:57 +0200 [thread overview]
Message-ID: <20230326153157.H3t5f1zf5jJ6Hx37UdGfkgefLQVIBfT1vE7AOtBv-Hw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42987@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/42987#issuecomment-1484132469
Comment:
imo, the proper way to use rust for development on void on most archs is to install the rustup package and use that to manage toolchain versions
this won't work for all archs because rustup doesn't have binaries for all the targets void supports but for most people it works
prev parent reply other threads:[~2023-03-26 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 21:14 [PR PATCH] " astralchan
2023-03-24 21:17 ` [PR PATCH] [Updated] " astralchan
2023-03-26 7:45 ` classabbyamp
2023-03-26 15:25 ` astralchan
2023-03-26 15:25 ` [PR PATCH] [Closed]: " astralchan
2023-03-26 15:31 ` classabbyamp [this message]
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=20230326153157.H3t5f1zf5jJ6Hx37UdGfkgefLQVIBfT1vE7AOtBv-Hw@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).