From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id cL5ACawBLF+AMAAA0tVLHw (envelope-from ) for ; Thu, 06 Aug 2020 13:12:12 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id EFvjBKwBLF9fZgAAbx9fmQ (envelope-from ) for ; Thu, 06 Aug 2020 13:12:12 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 0FFC3940668 for ; Thu, 6 Aug 2020 13:12:10 +0000 (UTC) Received: from localhost ([::1]:59358 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k3fgm-0001tV-Jm for larch@yhetil.org; Thu, 06 Aug 2020 09:12:08 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:46132) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k3fgT-0001rU-1Q for help-guix@gnu.org; Thu, 06 Aug 2020 09:11:49 -0400 Received: from lepiller.eu ([89.234.186.109]:40112) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k3fgQ-0008CG-OO for help-guix@gnu.org; Thu, 06 Aug 2020 09:11:48 -0400 Received: from lepiller.eu (localhost [127.0.0.1]) by lepiller.eu (OpenSMTPD) with ESMTP id 4aa97641 for ; Thu, 6 Aug 2020 13:11:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lepiller.eu; h=date :in-reply-to:references:mime-version:content-type :content-transfer-encoding:subject:to:from:message-id; s=dkim; bh=p4puwfTC696ek04FtPGaSmFyqTlsmVSWzsZNQiid3DU=; b=Kb0ZEXA+XMQA px06yArdEsClj/URWZPmDjyR9ogX2WxWENMPCx8nJSMvGJ5KJgRwMuGQrp5f/zPL zd0E7V7NCjBFDowuZO4OAuSFAPT0rmm9I7GJwQjhhz62dZOyRF0a1pJn/MCAGd7g HZ2m2AjN+GRELvUU6wxf1aMouO9ZX9+mAWrfNr3wVuUeGQe0a2HtZaTSyDV0MwA2 Vy2ttLv2XASZoQCEMzqYBjbr2q7crpJPn1eLhmUBSXhoCf2iQwUmQl8jO+4VOzkx 3t9odzmxYgw9JqCOJCDRZ+PO7x3guUTnuP6UJbnm7pFek3e9VGzmvsOh6o37c2U9 A2hG2dXtBQ== Received: by lepiller.eu (OpenSMTPD) with ESMTPSA id 4cce14cc (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for ; Thu, 6 Aug 2020 13:11:38 +0000 (UTC) Date: Thu, 06 Aug 2020 09:11:00 -0400 User-Agent: K-9 Mail for Android In-Reply-To: <30DXGCZPTPVS0.2349OUUUJIJ4B@wilsonb.com> References: <30DXGCZPTPVS0.2349OUUUJIJ4B@wilsonb.com> MIME-Version: 1.0 Subject: Re: Use guix to verify that code changes do not affect binary? To: help-guix@gnu.org From: Julien Lepiller Message-ID: Received-SPF: none client-ip=89.234.186.109; envelope-from=julien@lepiller.eu; helo=lepiller.eu X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/06 09:11:41 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=fail (body hash did not verify) header.d=lepiller.eu header.s=dkim header.b=Kb0ZEXA+; dmarc=fail reason="SPF not aligned (relaxed)" header.from=lepiller.eu (policy=none); spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Spam-Score: 1.09 X-TUID: 6p/7FybD0WPD 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=E5=B9=B48=E6=9C=886=E6=97=A5 2:41:07 GMT-04:00, elaexuotee@wilsonb= =2Ecom 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=2E > >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=2E > >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=2E However, the source hash >obviously >changes, so this idea is dead in the water=2E > >What I need is a way to verify whether build outputs change as I make >on the >`devel/foo' branch=2E Any brilliant ideas? > >Cheers!