From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix Date: Wed, 18 Jul 2018 21:45:51 -0700 Message-ID: <87601bkf40.fsf@gmail.com> References: <87fu45ve2z.fsf@gnu.org> <20180531144337.16298-1-ludo@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54555) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fg0qI-0008Sm-SM for bug-guix@gnu.org; Thu, 19 Jul 2018 00:47:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fg0qE-0002wS-0u for bug-guix@gnu.org; Thu, 19 Jul 2018 00:47:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:42394) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fg0qD-0002wD-RU for bug-guix@gnu.org; Thu, 19 Jul 2018 00:47:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fg0qD-0007MX-I1 for bug-guix@gnu.org; Thu, 19 Jul 2018 00:47:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20180531144337.16298-1-ludo@gnu.org> ("Ludovic \=\?utf-8\?Q\?Cou\?\= \=\?utf-8\?Q\?rt\=C3\=A8s\=22's\?\= message of "Thu, 31 May 2018 16:43:33 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 22629@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Ludo, Ludovic Court=C3=A8s writes: > Here is the =E2=80=9Cnew=E2=80=9D =E2=80=98guix pull=E2=80=99 that we dis= cussed notably in this thread: > > https://bugs.gnu.org/22629 Although I've been enjoying the new guix pull for a while now, I just today found the time to take a peek at these code changes. It's always educational to see how you write your code! I was surprised that "guix pull" doesn't build the guix package via the usual mechanisms (e.g., the way it would be built if I ran "guix build guix"). The new "guix pull" code builds a profile, so it seems like we could put packages in there (e.g., a guix package that inherits from the original but replaces the origin with a Git checkout). However, instead of re-using the build logic encapsulated in the guix package, it looks like we build Guix piece by piece using custom build logic in (guix self). Why do we do that? These improvements are great! I'm just curious about the motivation for the custom build logic. I'm guessing there is some sort of complication to simply using the guix package that is non-obvious, but I can't see what it is. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAltQF38ACgkQ3UCaFdgi Rp1ZBw//aibeMy1QxaCnUWh1W9vlZHJz8WyieYt6ivh3KEeiQk8UAgTe72MckmH7 MGCKKaztZVyezJeqzg6YNxOnGCHOfVPav/RdC6K8crrE3xw9XHFIZlFzxfp/BGnD 5n3nI7xTnrVqOhrNl/O7Hw+PKu/ICoZsT26TZhDG/rcxDauDdRFrId8fGEx+/I7k NcHIi25l2hRHbGEQa/9zmO+8XKRxqUzuhObl2pFDj8cU32I7MxkvVzlhYyJl8q6F rdFN3pthu49ljq8mr1ExcpqUCcrpW0aRnnYL6ONsd6JfgYqt++EsN049NA0Q5wd/ 9Fu5pk3OGUSD8/Xt3CG+nfnTmpqpDDHgUaF6AmB14Xm1melvgdjhx7l1IRcm6IwF phcDVFOKFQ96e2nVs6e4KzwC9/OQYpVsF07gPNTKewbmjC3jBIiq/4T5OTSw58f/ joB0Ne8eOvQ2iwz5CurTJJ/uW27Smlw5teSvzXKTZW/pzKGPvGC651cvmRRTicVK gYBdHu5A3ISIJLkkjZMrrervmPK2nwc0vgEV/YtCmT6LkFS3quXpyan8L/2M3S9y mc6EvfsQfLQ1vTFz5gD9ueY4ph22r8Gf2uEZk6zDm3MCLOk93/A9K6JWxxyxzsnR ICM1FZa/BXmNFldqnSjts9wm/BSCuhMGJ0L3WClwwZx1WcLzVsU= =Cdz8 -----END PGP SIGNATURE----- --=-=-=--