From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] build-style/cargo.sh: run cargo install with --locked
Date: Thu, 26 Sep 2019 01:00:22 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14729@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
There is a new pull request by jnbr against master on the void-packages repository
https://github.com/jnbr/void-packages cargo-install
https://github.com/void-linux/void-packages/pull/14729
build-style/cargo.sh: run cargo install with --locked
A patch file from https://github.com/void-linux/void-packages/pull/14729.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cargo-install-14729.patch --]
[-- Type: text/x-diff, Size: 895 bytes --]
From 8715effbd4aae9db5b8554224b688a3604fd059f Mon Sep 17 00:00:00 2001
From: Johannes <johannes.brechtmann@gmail.com>
Date: Thu, 26 Sep 2019 00:52:51 +0200
Subject: [PATCH] build-style/cargo.sh: run cargo install with --locked
Without --locked, cargo ignores the Cargo.lock file during install
and rebuilds the crate with updated dependencies.
This wastes time and makes builds unreproducable.
---
common/build-style/cargo.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/build-style/cargo.sh b/common/build-style/cargo.sh
index a2a0dfe3744..cff16bee082 100644
--- a/common/build-style/cargo.sh
+++ b/common/build-style/cargo.sh
@@ -18,6 +18,6 @@ do_install() {
: ${make_cmd:=cargo}
${make_cmd} install --path . --target ${RUST_TARGET} --root="${DESTDIR}/usr" \
- ${make_install_args}
+ --locked ${make_install_args}
rm "${DESTDIR}"/usr/.crates.toml
}
next reply other threads:[~2019-09-25 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 23:00 voidlinux-github [this message]
2019-09-26 13:11 ` [PR PATCH] [Merged]: " voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14729@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).