unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
* Use guix to verify that code changes do not affect binary?
@ 2020-08-06  6:41 elaexuotee
  2020-08-06 13:11 ` Julien Lepiller
  0 siblings, 1 reply; 2+ messages in thread
From: elaexuotee @ 2020-08-06  6:41 UTC (permalink / raw)
  To: help-guix


[-- 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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Use guix to verify that code changes do not affect binary?
  2020-08-06  6:41 Use guix to verify that code changes do not affect binary? elaexuotee
@ 2020-08-06 13:11 ` Julien Lepiller
  0 siblings, 0 replies; 2+ messages in thread
From: Julien Lepiller @ 2020-08-06 13:11 UTC (permalink / raw)
  To: help-guix

The only idea that comes to mind is to compare with something like that:

guix hash -r `guix build foo-devel`

Maybe others will have more brilliant ideas :)

On 2020年8月6日 2:41:07 GMT-04:00, elaexuotee@wilsonb.com wrote:
>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!

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-08-06 13:12 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-06  6:41 Use guix to verify that code changes do not affect binary? elaexuotee
2020-08-06 13:11 ` Julien Lepiller

unofficial mirror of help-guix@gnu.org 

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://yhetil.org/guix-user/0 guix-user/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-user guix-user/ https://yhetil.org/guix-user \
		help-guix@gnu.org
	public-inbox-index guix-user

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.gnu.guix.user
	nntp://news.gmane.io/gmane.comp.gnu.guix.user


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git