From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Packaging gx (for IPFS): Need to update default Go to 1.11? Date: Wed, 7 Nov 2018 13:26:42 -0500 Message-ID: <20181107182642.GA17483@jasmine.lan> References: <87d0rzxx15.fsf@ambrevar.xyz> <20181024141435.GA5988@jasmine.lan> <87efbyberv.fsf@ambrevar.xyz> <87d0ribeg2.fsf@ambrevar.xyz> <878t26b0i1.fsf@ambrevar.xyz> <20181106173116.GA3232@jasmine.lan> <87k1lqyuta.fsf@ambrevar.xyz> <20181106195712.GB6749@jasmine.lan> <87a7mlz6hv.fsf@ambrevar.xyz> <87o9b0n9gr.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58607) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gKTSX-00054K-U3 for guix-devel@gnu.org; Wed, 07 Nov 2018 14:25:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gKTSQ-0001ir-Ce for guix-devel@gnu.org; Wed, 07 Nov 2018 14:25:46 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:45819) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gKTSL-0001ds-0t for guix-devel@gnu.org; Wed, 07 Nov 2018 14:25:38 -0500 Content-Disposition: inline In-Reply-To: <87o9b0n9gr.fsf@ambrevar.xyz> 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: Pierre Neidhardt Cc: Guix-devel --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 07, 2018 at 05:22:44PM +0100, Pierre Neidhardt wrote: > Hmm, actually it seems that go1.9 is not able to build a package against > dependencies built with go1.11. Yeah, I don't think there is any notion of backwards compatibility there. > For Demlo, that would mean that I need to add the 1.9 specialization to 10 > packages, but this is brittle and it will conflict with other programs th= at > share some dependencies while using go1.11. >=20 > Suggestion? Maybe you could take a look at how we handle packaging for both Python 3 and Python 2? There, we have package variants for both Python versions, as necessary. --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlvjLmIACgkQJkb6MLrK fwiCMhAAtIW9VUxNH070u/lOV7yhXF4luNIadlXkkQaVCnZUcmC2srdh9UBCJXK1 GJQWXhK8VLIf9d8nhWksblNIeKoZMRQNmbLi/TiR+7mN1p8g9pt9HW/VyEDCCGTw 0Apw+pjEIepcmgTE4iJ5YzsM0IwOJKOPJKzJsdqlVClwFUi888tO1gShvz6F+ziT Lxdh5Ljin4WrB4ittyPyoUMkt73g6sSxV9CRSIZ6jiGaFFlwDBalhQWwXZzN3ssk Al4SFxhWnm6nSLnFJhnCOSQHoGrybFKZEQF5yIbFtDti5fhYD5GM6r9zUwd4TV/a 3TJDbRw9d/9QjNAoKCw1znoZwi0rKPl6xCerLFNqagFf3om9Ht7UUFUpRG4KHuUf t+N9u4aDRlHwNz80m8uWZt8RH8nhPI2nGAJ9yoROF235b8op0ooNoH7YMqveT1j0 aK/EOzfRjnuNBOI3MLwiXkIob5RiuYWv6OrX9IXbOhnfaVmp3Tm0tldqA+mwg6C9 rZZWhddP14ro8TEI+RDLggc8Be66f4pBD34QODYrBrf+koCPqnxrBGFvtYcuZQ8A lfCeGruPJLRqtalhPhjYLcM8mtu7xaJjwPGAV7yn7flk4kp+Al4Ocewkc2bC3mUK FdXiND6owkVyJLjZOGFTLNhOkjELUvEQzFhPnqgwF0+vMyJ6ehw= =B7QH -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5--