From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Some Rust packages build a lot of stuff during do_install
Date: Sun, 08 May 2022 03:37:09 +0200 [thread overview]
Message-ID: <20220508013709.s86Paj3cB7mqIxYloEE8QRBaPJEXwHA6oKvCsZn1gUM@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: 860 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/issues/29207#issuecomment-1120329925
Comment:
I've hit this in https://github.com/void-linux/void-packages/pull/37013, and I know what might be happening in the case of all of those packages. Essentially cargo arbitrarily decides to drop a feature from a transient dependency (with no indication of why). You can see it when comparing the command cargo runs at build and at install for the deepest dependency that gets rebuilt (the command is shown when adding `-vv`).
In the case of #37013, the dependency that gets rebuilt is `syn` because cargo drops its `full` feature. There's no apparent reason for that drop, and it might even be a bug somewhere. The short-term fix was to explicitly add that feature for that dependency in the top crate's Cargo.toml.
prev parent reply other threads:[~2022-05-08 1:37 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
2022-05-06 2:08 ` github-actions
2022-05-08 1:37 ` 0x5c [this message]
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=20220508013709.s86Paj3cB7mqIxYloEE8QRBaPJEXwHA6oKvCsZn1gUM@z \
--to=0x5c@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).