From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: guix-devel@gnu.org
Subject: The rust:cargo output - why?
Date: Thu, 23 Jul 2020 15:20:36 +0200 [thread overview]
Message-ID: <20200723132036.xxuy63acwe3dji7p@gravity> (raw)
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
Hi Guix,
I have noticed that the procedure we use to install cargo to a separate
output in the Rust definition has started rebuilding quite a large part
of the compiler when the prefix is changed starting in Rust 1.34. I have
asked around, and upstream doesn't support any straightforward way of
installing cargo to a separate prefix:
https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Installing.20cargo.20with.20a.20different.20prefix
I have some hacks in mind that could allow us to keep installing cargo
into a separate output without the extra rebuild, such as building the
compiler with --keep-stage or installing cargo with a DESTDIR and
manually moving the files. However, none of these, including the current
solution, are without tradeoffs. This makes me wonder - why not put
cargo in :out?
In my experience with using Rust, cargo is an integral part of the
toolchain and I find it quite unlikely that anyone would find bare rustc
useful. Indeed, rust is depended upon explicitly by cargo-build-system,
icecat and icedove, and all of these also use the cargo output.
User-facing usage is even more likely to use cargo.
As such, I would like to suggest that we merge rust:out and rust:cargo
on staging.
`guix size rust rust:cargo` reports that the closure would increase from
600 to 700 MiB.
Thoughts?
Regards,
Jakub Kądziołka
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-07-23 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 13:20 Jakub Kądziołka [this message]
2020-07-23 14:05 ` The rust:cargo output - why? John Soo
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=20200723132036.xxuy63acwe3dji7p@gravity \
--to=kuba@kadziolka.net \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).