From: Maxime Devos <maximedevos@telenet.be>
To: John Soo <jsoo1@asu.edu>
Cc: Paul Alesius <paul@unnservice.com>, guix-devel@gnu.org
Subject: Re: Packaging rust-analyzer is not necessary.
Date: Mon, 09 May 2022 21:06:58 +0200 [thread overview]
Message-ID: <ee070612d7e5c9b2b34a8c676ea6831460af20af.camel@telenet.be> (raw)
In-Reply-To: <871qyon06s.fsf@asu.edu>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
John Soo schreef op za 26-03-2022 om 09:33 [-0700]:
> > 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).
(responding to an old post)
FWIW, it turns out that Rust actually works well with Guix, only Cargo
doesn't, see reccent threads about antioxidant-build-system.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-09 19:07 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
2022-05-09 19:06 ` Maxime Devos [this message]
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=ee070612d7e5c9b2b34a8c676ea6831460af20af.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
--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.