From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Guix & IPFS Date: Mon, 15 Oct 2018 12:40:18 +0200 Message-ID: <87lg6zjxwt.fsf@ambrevar.xyz> References: <87r2grk5dj.fsf@ambrevar.xyz> <87lg6zfr20.fsf@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]:48144) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gC0Ic-0004yB-BM for guix-devel@gnu.org; Mon, 15 Oct 2018 06:40:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gC0IV-0002b4-K1 for guix-devel@gnu.org; Mon, 15 Oct 2018 06:40:32 -0400 In-reply-to: <87lg6zfr20.fsf@gnu.org> 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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Guix-devel --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > FWIW Pierre-Antoine (who was working with me as an intern on Guix-HPC) > has given me the last revision of the gopkg importer, which I=E2=80=99m p= lanning > to include soon. It might be useful to you! Absolutely! Could you share the code now so that I can start using it? Th= anks! > This seems to be the same for all Go packages: they specify the exact > commit of each of their dependencies, AIUI. No, Go programs typically refer only to repositories, not to their commit. = This is precisely why it's a problem. Golang's dependency management was not ve= ry well designed I'm afraid. Misunderstanding? > In practice it may be that upgrading will often be fine, but it does > mean that every time we upgrade a Go package, we have to build > everything =E2=80=9Cguix refresh -l GO-PACKAGE=E2=80=9D reports to make s= ure. Yup, but it's also the case with any other package, isn't it? > > - gx retrieves the deps over IPFS: how important is this? Should we do > > the same? What about using "gx"? We could also implement a new > > "gx-fetch" method fully written in Guile. > > In Guix dependencies are listed statically in the =E2=80=98inputs=E2=80= =99 fields, so I > suppose we have to run it once to retrieve that list and then =E2=80=9Cen= code=E2=80=9D > it as =E2=80=98inputs=E2=80=99, no? Sorry, I meant "ipfs-fetch", so we might be talking about different things = :p =2D Network: it would be nice to be able to retrieve packages over IPFS. W= e can do this without IPFS, just like "gx" does. =2D Importer: I don't know how Pierre-Antoine retrieves dependencies, but technically it's enough to download the package and run some "go ..." com= mand to list deps. In the case of go-ipfs (and possibly other Go packages usi= ng gx), we can only list the deps with "gx deps...". Note that in both base= s the package does not have to be built, if I'm not mistaken. Makes sense? =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlvEbpIACgkQm9z0l6S7 zH9EwAgAgimqMwQOJTNlYPAVVjz3NwWEtCisX03dD79gVjZBZ0FnFb4YcgihnuK6 yr9sNpKXZoKCU8I9qoP3O8z9DnLEoyWrJVIvg02S6Zi5fHeOIpxJNs2OTywXKG3g wg4Eha6BbsUPy+iteoBEPaGeAHp5v/YHI80xH7p730mdoVPYG9uZn3g0CPBQKjdk ZureLstMZkel8WAHSXVbpCOCWGgu1DAmzGv3rFA3bs0IDNyYa4oUn3CVfbhGyGUT iGD5XQg1rWIu4fQVJROjc/eARWhULwWigI7mmJ+bjKtneTbpHcLKw4z/htVsYWL+ onOeSo8ebmhTgBBsmeE6+ss3Th1tCA== =osIi -----END PGP SIGNATURE----- --=-=-=--