From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D45C7138BF3 for ; Sat, 15 Feb 2014 22:44:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 901D7E0A97; Sat, 15 Feb 2014 22:43:53 +0000 (UTC) Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com [209.85.214.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A944EE0A7C for ; Sat, 15 Feb 2014 22:43:52 +0000 (UTC) Received: by mail-ob0-f179.google.com with SMTP id wo20so15365241obc.24 for ; Sat, 15 Feb 2014 14:43:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=D8md7i6dPRysbpX+3hjjSEFpl5lBkPwj+0jzhXEcVTw=; b=EqFJvOv6bdGAZ9JbZbWnFlpEf9Vz2GG0rJ+AjJZKWvExaAsxvyzx6C5U4HsARJfIGj NLlbYj85VUTF/CayW5drmHsadScPadRrKp4hvs8C/gq6Q65GoELP40DE8CezDHvEIuEu OXw1u90r2JpSfeYDov7Dirg6Clu0s+XZ+ImxLIjOfZ5sWMa9LnLBb7OhKUBPtRl77xij q3KGLJeONpyJjvlQXmheZPs418LZOvsGMJMTDI6D9/Zx1A21+9yNjU1NW6Avl0chp+yJ CfiBpp8oHR5+dLsEWRNxgVcscrNO8MLLbX56x0HTW8aYYP136LFHFY4eKKh0bsmfhcCw mlVg== X-Received: by 10.182.131.170 with SMTP id on10mr13553596obb.2.1392504231517; Sat, 15 Feb 2014 14:43:51 -0800 (PST) Received: from laptop (cpe-76-187-91-128.tx.res.rr.com. [76.187.91.128]) by mx.google.com with ESMTPSA id o7sm69035287oed.3.2014.02.15.14.43.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Feb 2014 14:43:49 -0800 (PST) Sender: William Hubbs Received: by laptop (sSMTP sendmail emulation); Sat, 15 Feb 2014 16:44:09 -0600 Date: Sat, 15 Feb 2014 16:44:09 -0600 From: William Hubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] dev-lang/go Message-ID: <20140215224409.GA1593@laptop.home> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20131230154817.34a69433@ciguri> <20140211013844.4057ddb2@gentoo.org> <20140213175916.GA1919@laptop.home> <20140214133010.153a46b8@deathstar> <20140214110249.27842f70@ciguri> <20140215004844.49e9b7f2@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <20140215004844.49e9b7f2@gentoo.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 83e61e8c-afb8-4a00-bad2-c9250c82ed31 X-Archives-Hash: 66dcd101747afbdc7e881b04f32421f6 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 15, 2014 at 12:48:44AM +0100, yac wrote: > On Fri, 14 Feb 2014 11:02:49 -0500 > Emery Hemingway wrote: > > The default GOROOT that go looks at for base libraries seems to be > > compiled in so this should be pretty easy, like python but simplier. >=20 > I'm not sure what you are trying to solve here. Afaik GOROOT is used to > determine where to install and it can be overriden from env. Not overridden, but extended. See go help gopath. > > An eclass could look at a GO_MINIMUM variable and install for each > > version go that is present and matches. >=20 > It might be good idea to learn from others who'd been through this and > I think the new python eclasses are good ones, going with something > like PYTHON_TARGETS array (GOLANG_TARGETS ?) =20 I would prefer go_targets if this becomes an issue, but it isn't at this point because there is only one target, go1, and we do not know if there will be a go2 or not. > > Dropping old versions of go > > will be easy because linking wont break, and new releases should be > > forwards compatible. >=20 > So far yes I think but I guess that may be quite different with in the > future with >1.x, and "should be" so there may be corner cases where the > user does need to use earlier version. Highly unlikely in the context of go1, and again, we don't know if there is going to even be a go2 or not. The only reason there will be a go2 is if there needs to be a change at the source level which can only be done in a backward incompatible way. The question really should be, do we want a system-wide workspace to store third-party libraries [1]? and if so, where do we put it -- maybe /usr/lib/go-gentoo should exist along side /usr/lib/go? The catch would be that every time you upgrade dev-lang/go, everything stored in /usr/lib/go-gentoo has to be recompiled because there is no guarantee that the libraries we have there are compatible with each minor release of go1, only the source. Then, the executables we have in /usr/bin will still run, but it would be good to rebuild them as well to get the new libraries linked into them. If we had a work space in, say, /usr/lib/go-gentoo, we could leave the executables in there and symlink them to /usr/bin. If we did that, it would be easy for a user to rebuild everything in the workspace for the new go by doing emerge /usr/lib/go-gentoo/bin Thoughts? William [1] http://golang.org/doc/code.html --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlL/7bkACgkQblQW9DDEZThBVACfXTviC5ce6PlHuYyk2d5pEXkb hMMAnRBdvfW89hdzKjvZZN1avmY76uzG =u5HV -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi--