From: Tobias Geerinckx-Rice <me@tobias.gr>
To: "Todor Kondić" <tk.code@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: rust: where is cargo?
Date: Sat, 26 Dec 2020 16:02:33 +0100 [thread overview]
Message-ID: <87czywsj92.fsf@nckx> (raw)
In-Reply-To: <Xh2XBgOGD3ab_YKl9rw5nsl394YjpNQpUZP4-aDv9xvLAKawPot6xd0-M3C5UHss2ezhMO8RZvXy3wc1Q2xucFmdbohZNSVR_0FK57Exb7E=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
Hi Todor!
Todor Kondić 写道:
> I have been playing with rust and the first thing I noticed with
> the guix installation is that there is no cargo.
There is, in the (as you note) cargo output:
$ guix install rust:cargo
$ type cargo
cargo is /home/nckx/.guix-profile/bin/cargo
$ realpath `command -v cargo`
/gnu/store/krn8958...-rust-1.46.0-cargo/bin/cargo
$ cargo search guix
guix = "0.1.0" # Cross Platform Gui Library
# wait whut no
I think we'll need more details to know why/what doesn't work for
you.
How did you install and test 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).
Then your configuration is broken somehow: something is messing
with Guix's $PATH.
Do you modify $PATH anywhere, for example in your .bash_profile?
> I know that guix approach is to replace package managers
I don't think that's true.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-12-26 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 14:34 rust: where is cargo? Todor Kondić
2020-12-26 15:02 ` Tobias Geerinckx-Rice [this message]
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=87czywsj92.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=tk.code@protonmail.com \
/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).