From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id B1D0A138334 for ; Mon, 9 Sep 2019 21:46:26 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0C050E092A; Mon, 9 Sep 2019 21:46:21 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BB5E9E091F for ; Mon, 9 Sep 2019 21:46:20 +0000 (UTC) Received: from whubbs1.gaikai.biz (unknown [100.42.103.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: williamh) by smtp.gentoo.org (Postfix) with ESMTPSA id 478A534AF41 for ; Mon, 9 Sep 2019 21:46:19 +0000 (UTC) Received: (nullmailer pid 32660 invoked by uid 1000); Mon, 09 Sep 2019 21:46:16 -0000 Date: Mon, 9 Sep 2019 16:46:16 -0500 From: William Hubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] rfc: go 1.13 and go modules Message-ID: <20190909214616.GA32528@whubbs1.dev.av1.gaikai.org> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20190909173418.GA30003@whubbs1.dev.av1.gaikai.org> <20190910083517.1877fd18@katipo2.lan> 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <20190910083517.1877fd18@katipo2.lan> User-Agent: Mutt/1.10.1 (2018-07-13) X-Archives-Salt: 4009af44-a692-4546-9b38-21a946735dba X-Archives-Hash: 8431af09b5d1a6c5cf3ba45088087b72 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 10, 2019 at 08:35:17AM +1200, Kent Fredric wrote: > On Mon, 9 Sep 2019 12:34:18 -0500 > William Hubbs wrote: >=20 > > There is another option I want to try which is adding "go mod vendor" to > > src_unpack for go packages. >=20 > Is it infeasible to write a tool that you execute as a maintainer, that s= imulates > what "go mod vendor" would do, but instead emits a list of entries for SR= C_URI, > and then have an eclass or something construct the vendor dir from those? >=20 > That's what is available for rust stuff. I'm not sure how feasible something like that is. $ go list -m all will list the dependencies of a module, but that doesn't look like it can be translated into src_uri format. You would basically have to parse go.mod exactly the way upstream does it and come up with a way to download the correct versions of the source. William --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTVeuxEZo4uUHOkQAluVBb0MMRlOAUCXXbIEgAKCRBuVBb0MMRl OPpEAJ99mtVFbqnR84tjn4aq/EKDn8nD8QCfTGqso9INykSa1aADDnAVqGc/0IE= =BlNp -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE--