From: "Todor Kondić" <tk.code@protonmail.com>
To: "help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: rust: where is cargo?
Date: Sat, 26 Dec 2020 14:34:44 +0000 [thread overview]
Message-ID: <Xh2XBgOGD3ab_YKl9rw5nsl394YjpNQpUZP4-aDv9xvLAKawPot6xd0-M3C5UHss2ezhMO8RZvXy3wc1Q2xucFmdbohZNSVR_0FK57Exb7E=@protonmail.com> (raw)
Hello,
I have been playing with rust and the first thing I noticed with the guix installation is that there is no cargo. More accurately, there is indeed an output of the rust package called "cargo" and there are entries for cargo with bin paths in the store, but nothing that ends up in the PATH variable (etc/profile).
So, what's the deal here? I know that guix approach is to replace package managers, but cargo is more than that and, at least, a tool needed to follow the rust book while learning.
next reply other threads:[~2020-12-26 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 14:34 Todor Kondić [this message]
2020-12-26 15:02 ` rust: where is cargo? Tobias Geerinckx-Rice
2020-12-26 18:19 ` Adonay Felipe Nogueira via
2020-12-26 19:16 ` Adonay Felipe Nogueira via
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='Xh2XBgOGD3ab_YKl9rw5nsl394YjpNQpUZP4-aDv9xvLAKawPot6xd0-M3C5UHss2ezhMO8RZvXy3wc1Q2xucFmdbohZNSVR_0FK57Exb7E=@protonmail.com' \
--to=tk.code@protonmail.com \
--cc=help-guix@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.
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).