unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: mikadoZero <mikadozero@yandex.com>
To: help-guix <help-guix@gnu.org>
Subject: Rust development tools
Date: Wed, 17 Apr 2019 22:26:39 -0400	[thread overview]
Message-ID: <cuca7go2gm8.fsf@yandex.com> (raw)

The rust book is a learning resource for the rust programming language.
https://doc.rust-lang.org/book/title-page.html

It includes content on these rust development tools:

* cargo
  + build system and package manager
  + provides dependency management
  + used through the entire rust book
  https://doc.rust-lang.org/book/ch01-03-hello-cargo.html

* rustup
  + adding the developer tool below
    https://doc.rust-lang.org/book/appendix-04-useful-development-tools.html
  + using other versions of rust like nightly
    - example of using nightly rust
      https://rocket.rs/v0.4/guide/getting-started/

* developer tools
  https://doc.rust-lang.org/book/appendix-04-useful-development-tools.html
  + rustfmt - code style reformatter
  + clippy - linting
  + rls - language server

I have rust installed on a Guix System.  It does not look like it
included any of these developer tools.  They also do not show up when
doing a package search for their names or for just rust.  I have also
searched for them with a `locate rust` and filtered its results with
sed.

What would be other ways to find these if they are already packaged for
Guix?

If cargo is not packaged are people who are using rust with Guix System
using rustc and manually managing their dependencies?

Are there any special considerations for Guix packages that provide
programs like cargo and rustup that are also package managers?

How does Guix deal with something like rust nightly releases if at all?

             reply	other threads:[~2019-04-18  2:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18  2:26 mikadoZero [this message]
2019-04-18 15:47 ` Rust development tools Ivan Petkov
2019-04-18 19:45   ` John Soo
2019-04-18 20:23   ` mikadoZero
2019-04-19  2:40     ` Ivan Petkov
2019-04-24 16:52       ` mikadoZero

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=cuca7go2gm8.fsf@yandex.com \
    --to=mikadozero@yandex.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).