From: John Soo <jsoo1@asu.edu>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guix-devel@gnu.org, Paul Alesius <paul@unnservice.com>
Subject: Re: Packaging rust-analyzer is not necessary.
Date: Sat, 26 Mar 2022 09:33:15 -0700 [thread overview]
Message-ID: <871qyon06s.fsf@asu.edu> (raw)
In-Reply-To: <a098b294d1149bcadc4bf713897c530771bfd927.camel@telenet.be> (Maxime Devos's message of "Sat, 26 Mar 2022 16:30:49 +0100")
Hi Paul And Maxime,
> Even if you didn't succeed at updating _all_ dependencies, if you
> have patches for some of them, please send them. It will help people
> in the future with updating rust-analyzer or other rust packages.
I had a patchset (here: https://issues.guix.gnu.org/46162) adding rust-analyzer and the rest of the other tools that come part of the rust tree. I think it would not be too much work to add if added as outputs/companion packages to rust itself.
> For many people, a vaguely recent-ish version would be sufficient. At
> least, that's the case for C, GCC and Clang.
> ...
> It might be possible to do "cargo xtask install --server", but many
> advantages of Guix would be lost.
That worked for me. I was using guix' rust tooling for my job. I much prefer using guix over rustup/cargo. I just had to patch rust a lot and my patches haven't made it in (yet?).
> Indeed, e.g. it would be nice to figure out how to eliminate #:skip-
> build?, replace #:cargo-inputs by regular inputs, figure out how to
> stop having to package multiple versions of the same package.
My gut feeling is still that the functional package managers need to collaborate with the rust/cargo team. Rust itself just does not lend itself well to the model. It is a shame since we share many of the same goals (reproducibility and reliability come to the top of mind).
Kindly,
John
next prev parent reply other threads:[~2022-03-26 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 8:05 Packaging rust-analyzer is not necessary Paul Alesius
2022-03-26 15:30 ` Maxime Devos
2022-03-26 16:33 ` John Soo [this message]
2022-05-09 19:06 ` Maxime Devos
2022-03-28 23:50 ` Improving importers best investment for growing gnu/packages/ Brendan Tildesley
2022-03-29 9:01 ` Maxime Devos
2022-03-29 10:30 ` Brendan Tildesley
2022-03-29 19:03 ` Liliana Marie Prikler
2022-05-02 9:19 ` zimoun
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=871qyon06s.fsf@asu.edu \
--to=jsoo1@asu.edu \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=paul@unnservice.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.