From: elaexuotee@wilsonb.com
To: help-guix@gnu.org
Subject: Use guix to verify that code changes do not affect binary?
Date: Thu, 06 Aug 2020 15:41:07 +0900 [thread overview]
Message-ID: <30DXGCZPTPVS0.2349OUUUJIJ4B@wilsonb.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 821 bytes --]
Hello Guix,
I am hacking on the build scripts of an existing project and need to make sure
that my changes do not affect the actual build products.
Is there a good way to leverage guix for this?
Previously, I had been doing this manually by (deterministically) tarring up
the build products and comparing hashes; however, this is a bit prone to
me flubbing up the tar-hash-compare process.
For a brief moment, I thought I could write a package definition that points to
a specific `devel/foo' branch of my repo and then have `guix build --check`
compare builds as I update the branch head. However, the source hash obviously
changes, so this idea is dead in the water.
What I need is a way to verify whether build outputs change as I make on the
`devel/foo' branch. Any brilliant ideas?
Cheers!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next reply other threads:[~2020-08-06 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 6:41 elaexuotee [this message]
2020-08-06 13:11 ` Use guix to verify that code changes do not affect binary? Julien Lepiller
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=30DXGCZPTPVS0.2349OUUUJIJ4B@wilsonb.com \
--to=elaexuotee@wilsonb.com \
--cc=help-guix@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.
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).