From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tobias Geerinckx-Rice Subject: Re: native-inputs ending up as run-time references [was: ISO image available for testing!] Date: Wed, 6 Dec 2017 04:48:47 +0100 Message-ID: References: <87infv54m3.fsf@gnu.org> <87efqgnn7x.fsf@elephly.net> <878teo59tb.fsf@gnu.org> <20171201183042.GB2504@jasmine.lan> <87tvxadz11.fsf@elephly.net> <87lgiirhsf.fsf_-_@gnu.org> <874lp618iy.fsf@cbaines.net> <87shcoaj2w.fsf@gnu.org> <87bmjcvft3.fsf@netris.org> <20171206031809.GB28118@jasmine.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="a4LwC6nAwF87FlaIPbQ4dUOJtgipcqewM" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46467) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eMQf8-0006F2-3O for guix-devel@gnu.org; Tue, 05 Dec 2017 22:46:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eMQf7-000703-8d for guix-devel@gnu.org; Tue, 05 Dec 2017 22:46:22 -0500 In-Reply-To: <20171206031809.GB28118@jasmine.lan> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: leo@famulari.name Cc: guix-devel@gnu.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --a4LwC6nAwF87FlaIPbQ4dUOJtgipcqewM Content-Type: multipart/mixed; boundary="4k9DtMkT3AuWQQb3kxc1uBEvfW68aNLgE"; protected-headers="v1" From: Tobias Geerinckx-Rice To: leo@famulari.name Cc: ludo@gnu.org, mhw@netris.org, guix-devel@gnu.org Message-ID: Subject: Re: native-inputs ending up as run-time references [was: ISO image available for testing!] References: <87infv54m3.fsf@gnu.org> <87efqgnn7x.fsf@elephly.net> <878teo59tb.fsf@gnu.org> <20171201183042.GB2504@jasmine.lan> <87tvxadz11.fsf@elephly.net> <87lgiirhsf.fsf_-_@gnu.org> <874lp618iy.fsf@cbaines.net> <87shcoaj2w.fsf@gnu.org> <87bmjcvft3.fsf@netris.org> <20171206031809.GB28118@jasmine.lan> In-Reply-To: <20171206031809.GB28118@jasmine.lan> --4k9DtMkT3AuWQQb3kxc1uBEvfW68aNLgE Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable Leo, Leo Famulari wrote on 06/12/17 at 04:18: > I think of "run-time references" as explicit store references > (file-names) found in the build output by the post-build reference > scanner and recorded in /var/guix/db. These references are what graftin= g > rewrites. All right, that was my idea too (though there might be some sloppiness in my mental model yet). > `guix gc --references` can be used to query the database for a given > store item. > > `guix graph`, on the other hand, shows the graphs of package > definitions. That is, the list of inputs, native-inputs, > propagated-inputs, etc. Some of these inputs could be totally > superfluous, and the build output would ideally not contain any > explicit references to them at all. Thanks for the clarification! I've never actually found a use for =E2=80=98= guix graph=E2=80=99 myself, but can't imagine a Guix talk without it. :-) Unfortunately, I sent you after a red herring: =E2=80=98graph=E2=80=99 wa= s a typo. I did, in fact, mean =E2=80=98guix gc=E2=80=99: $ guix gc --references `guix build ghc` | grep perl /gnu/store/9g4fpfz86vjkx83v5696vm5dzg2sc9qj-perl-5.26.0 $ grep -r /gnu/store/9g4fpfz86vjkx83v5696vm5dzg2sc9qj-perl-5.26.0 \ `guix build ghc` .../ghc-split:#!/gnu/store/...-perl-5.26.0/bin/perl .../settings: ("perl command", "/gnu/store/...-perl-5.26.0/bin/perl"), And: $ guix gc --references `guix build ghc-haddock-library` | grep hspec-d /gnu/store/xfh89fmdn2xvd4aw76164zqz0941xw01-hspec-discover-2.2.0 $ grep -r xfh89fmdn2xvd4aw76164zqz0941xw01-hspec-discover-2.2.0 \ `guix build ghc-haddock-library` [very long paths snipped with great prejudice] Binary file /gnu/store/.../package.cache matches Binary file /gnu/store/.../libHShaddock-library-1.2.1-...-ghc7.10.2.so matches > The term "reference" has a few meanings in Guix, but I think that Mark > is talking about explicit store paths. I'm afraid we're on the same page then. Kind regards, T G-R --4k9DtMkT3AuWQQb3kxc1uBEvfW68aNLgE-- --a4LwC6nAwF87FlaIPbQ4dUOJtgipcqewM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCWidonw0cbWVAdG9iaWFz LmdyAAoJEA2w/4hPVW15WYQA/1/9ClQKj+jPzU39ZIFTNRaLVdU7TvdI68FpeUyc M2llAP4i9QPo4byZ430QXDbW1g54zKdpGfbOeLpWXGC/Z8BqDQ== =ThGW -----END PGP SIGNATURE----- --a4LwC6nAwF87FlaIPbQ4dUOJtgipcqewM--