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 7769A138334 for ; Wed, 11 Sep 2019 19:26:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AA3F1E0A9E; Wed, 11 Sep 2019 19:26:04 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (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 5A905E0A93 for ; Wed, 11 Sep 2019 19:26:04 +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 0D48134B13A for ; Wed, 11 Sep 2019 19:26:02 +0000 (UTC) Received: (nullmailer pid 19601 invoked by uid 1000); Wed, 11 Sep 2019 19:26:00 -0000 Date: Wed, 11 Sep 2019 14:26:00 -0500 From: William Hubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [PATCH 3/3] dev-vcs/hub: migrate to go-module.eclass Message-ID: <20190911192600.GA19575@whubbs1.dev.av1.gaikai.org> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <20190911172128.18885-1-williamh@gentoo.org> <20190911172128.18885-4-williamh@gentoo.org> <20190911174720.GA19146@whubbs1.dev.av1.gaikai.org> <20190912071528.625d479e@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="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: <20190912071528.625d479e@katipo2.lan> User-Agent: Mutt/1.10.1 (2018-07-13) X-Archives-Salt: ac87ef71-b250-4fd7-8eee-907b8358c35e X-Archives-Hash: 242006801349cd681a5cd56ca2a4eece --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 12, 2019 at 07:15:28AM +1200, Kent Fredric wrote: > On Wed, 11 Sep 2019 12:47:20 -0500 > William Hubbs wrote: >=20 > > Sorry, That train already left the station with the golang-* eclasses > > and there is nothing we can do about it. >=20 > Saying "this creates a legal problem" followed by "eh, nothing we can > do about it, carry on" really doesn't work in reality, as far as I'm > aware. >=20 > Usually if you find yourself rationalizing around a legal problem, you > end up getting bitten by said legal problem. After chatting a bit more about this on IRC, let me clarify. This is an issue that is not related to the eclass, but an example package (patch 3 isn't the eclass, it is just an example of how to use it). There is no LICENSE setting in the eclass, so it doesn't affect the eclass. What I was advised is that we are all supposed to audit our packages and make sure LICENSE=3D is correct. William --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTVeuxEZo4uUHOkQAluVBb0MMRlOAUCXXlKQgAKCRBuVBb0MMRl OJF9AKCsOeTvC5h1F+A7+Cd5r00RYFkVdQCcD+dY4PQdiTUPGV3B68Ex/uuVreQ= =mJ7I -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/--