From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Fwd: Re: Guix & IPFS Date: Tue, 16 Oct 2018 12:19:01 +0200 Message-ID: <87zhvei48a.fsf@ambrevar.xyz> References: <87r2grk5dj.fsf@ambrevar.xyz> <87lg6zfr20.fsf@gnu.org> <87lg6zjxwt.fsf@ambrevar.xyz> <871s8rfmoe.fsf@gnu.org> <87a7nfjrml.fsf@ambrevar.xyz> <877eijjot7.fsf@ambrevar.xyz> <20181015140856.xd3de5hkumtaueer@thebird.nl> <8736t6jkpu.fsf@ambrevar.xyz> <20181016094752.slvicfgd2rjy57u2@thebird.nl> <871s8qjjdh.fsf@ambrevar.xyz> 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]:48113) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gCMRT-0001o1-BX for guix-devel@gnu.org; Tue, 16 Oct 2018 06:19:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gCMRO-0004wv-9b for guix-devel@gnu.org; Tue, 16 Oct 2018 06:19:11 -0400 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: Guix-devel , Ludovic =?utf-8?Q?Court=C3=A8s?= , Pjotr Prins --==-=-= Content-Type: multipart/mixed; boundary="=-=-=" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Re-including everyone in the conversation: Pierre Neidhardt writes: >> > Otherwise I'll just go with the first method and patch the IPFS source= to use >> > the local dependencies. >> >> Also fine. > > Hmm, on second thought, I'm not so sure. It's a slippery slope and in th= e long > run, I doubt we could easily make sure the Guix packaged dep corresponds = to the > IPFS-path dep in the source. > > There is a conversation upstream: > > https://github.com/ipfs/go-ipfs/issues/5054 > > To quote one of the developers: > >> > We need to build IPFS downstream in Debian from reusable packaged libr= aries. >> Don't do that. We havent tested and verified ipfs with those dependencie= s. We >> have tested and verified ipfs with exactly the dependencies that we ship= it >> with. Building ipfs with other dependencies is just begging for somethin= g to >> go wrong that will be super annoying for me to have to debug. If debian = starts >> shipping an ipfs built with dependencies of their choosing, my response = to any >> bug report from a debian user will be "please use a version of ipfs comp= iled >> from canonical source" > > So I think the best idea at the moment is to write a gx-fetcher. > It could look like the following: > > --8<---------------cut here---------------start------------->8--- > (define-public ipfs-go-ipfs-config > (let ((ipfs-hash "QmSoYrBMibm2T3LupaLuez7LPGnyrJwdRxvTfPUyCp691u")) > (package > (name "ipfs-go-ipfs-config") > (version (gx-version "0.2.13" revision ipfs-hash)) > (source > (origin > (method gx-fetch) > (uri (gx-reference ipfs-hash)) > (file-name (gx-file-name name version)) > (sha256 > (base32 > "0qk6fshgdmhp8dip2ksm13j6nywi41m9mn0czkvmw6b697z85l2r")))) > (build-system go-build-system) > (arguments > '(#:unpack-path (string-append "gx/ipfs/" ipfs-hash "/go-ipfs-con= fig") > #:import-path (string-append "gx/ipfs/" ipfs-hash "/go-ipfs-con= fig"))) > (home-page > "https://github.com/ipfs/go-ipfs-config") > (synopsis "...") > (description "...") > (license license:expat)))) > --8<---------------cut here---------------end--------------->8--- > > What about a gx-build-system? It would inherit from go-build-system and > automate the (string-append "gx/ipfs" ...) part. Don't know if it's wort= h it. =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature Content-Disposition: attachment; filename=signature.asc Content-Transfer-Encoding: base64 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRRXpCQUVCQ0FBZEZpRUVVUE0rTGxzTVBa QUVKS3ZvbTl6MGw2Uzd6SDhGQWx2RnVDc0FDZ2tRbTl6MGw2UzcKekgrTEpBZjhEOUMzc25ONkRF Z1pCSFAzaStwbSttY2FLS3U5ZzhKTTZVWHRIc21GNGJYSzcyRjZsWUVOdm10VAp5SzRDcXJqV1JM cWtibE5YQ1ZtZ0N0TCtJSlhiakNjODJ0RXROL1ROWkl6c3FFK0kvZVlvM25vRVh4SHNIc0hjClp0 YkgyN21ocVdRSjJFdmNBRHQwaWt3ZVM0QmU5MlZoU2ZmR0xwWUdQK2hvQWo3aGV4RWpPZWh4OGlo cSttejIKZkNicU83bzVteEZ5S2NzUzVtY1QvUkZtbFBrTWw5d3pyQ0wxQ2JDUU83dzZjWVlhTkNo ZTlOMGF3dXI4dGNIdgpjYlVEVjE0SXNnN1pwNitrUHYrTnJVUC9pQkdjVitVeWdKcTFCQXVPRFRO QUE0aWFEeXVaWUYvTDZaL1hqdEkrCnBCaG9IV0xTbU5CZGs2WE5XL3NwZ1BWcmhoNUxsZz09Cj1W SEJUCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ== --=-=-=-- --==-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlvFuxUACgkQm9z0l6S7 zH+OMggAlcKRzJCroXRzaBnTpOQkg+j13/2dOwDGlQ0kMgn9btD6i/5FMJqZsWxm FmZ7WJ99AcWSzmwJ7SOeJgmHv5KCYHiE2Nlj2zLxkBSIYfQOzwZC/o8WnkGq/K/g k/tzt015txuDBOpzeOn7Qq0mgig5QDmRyCrh8wlfXm7fnmdEPJDD3eh9IAbeolkS YJgA5AWQOZ+kesqMTInZ9lBMAMJXkbwsgOjo9o8v11CwsyVlDE5xqHxqRnRW4ISN FKYSyCCXOU8djVyvRmDAJ4Jsv1EYlIDgfhf1zxMA2jcLaykmKBCh1uCF7vbFOeah 0jvZsz+LM1rkt/5XLXIqg5h6XnJM5Q== =yJoE -----END PGP SIGNATURE----- --==-=-=--