From: gbrlsnchs <gbrlsnchs@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Some Rust packages build a lot of stuff during do_install
Date: Tue, 16 Mar 2021 00:49:35 +0100 [thread overview]
Message-ID: <20210315234935.MxHg2Q24XwQNYKGtg52jeis89bYhf9o6Qdcp_0ba6n4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29207@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
New comment by gbrlsnchs on void-packages repository
https://github.com/void-linux/void-packages/issues/29207#issuecomment-799828820
Comment:
This *might* have something to do with [this issue](https://users.rust-lang.org/t/cargo-install-triggering-new-compilation-after-cargo-build/54123) I reported on Rust forums ([now reported on Cargo's repo too](https://github.com/rust-lang/cargo/issues/9272)). Overriding `do_install` to just grab the binary generated during `do_build` makes total sense to me. :slightly_smiling_face:
next prev parent reply other threads:[~2021-03-15 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 15:12 [ISSUE] " ericonr
2021-03-03 16:09 ` leahneukirchen
2021-03-15 23:28 ` gbrlsnchs
2021-03-15 23:49 ` gbrlsnchs [this message]
2022-05-06 2:08 ` github-actions
2022-05-08 1:37 ` 0x5c
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=20210315234935.MxHg2Q24XwQNYKGtg52jeis89bYhf9o6Qdcp_0ba6n4@z \
--to=gbrlsnchs@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).