From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: tectonic: remove hardcoded versions
Date: Sun, 15 Sep 2019 18:07:42 +0200 [thread overview]
Message-ID: <20190915160742.Se_6vNNDqBPX_i2JsSKCzHSl1NYmQiWLJXA2D-R1RSw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14463@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/14463#issuecomment-531577954
Comment:
cargo packages usually comes with `Cargo.lock`, which makes sure it is using a fixed version.
We don't run `cargo update` each build, resulting in building the same code each time the revision is bumped. If you start selectively updating some random dependencies to the latest revision available you get different binaries every time the package is build.
Checking out a version of a void template should optimally produce exactly the same binaries as the previous build, the build date shouldn't have influence on the produced binaries.
next prev parent reply other threads:[~2019-09-15 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 23:46 [PR PATCH] " voidlinux-github
2019-09-15 12:00 ` voidlinux-github
2019-09-15 15:31 ` voidlinux-github
2019-09-15 15:45 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-15 15:45 ` voidlinux-github
2019-09-15 16:07 ` voidlinux-github [this message]
2019-09-15 16:10 ` voidlinux-github
2019-09-15 16:11 ` voidlinux-github
2019-09-15 20:18 ` [PR PATCH] [Closed]: " voidlinux-github
2019-09-15 20:18 ` 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=20190915160742.Se_6vNNDqBPX_i2JsSKCzHSl1NYmQiWLJXA2D-R1RSw@z \
--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).