On Thu, Sep 12, 2019 at 07:15:28AM +1200, Kent Fredric wrote:
> On Wed, 11 Sep 2019 12:47:20 -0500
> William Hubbs <williamh@gentoo.org> wrote:
> 
> > Sorry, That train already left the station with the golang-* eclasses
> > and there is nothing we can do about it.
> 
> 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.
> 
> 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= is correct.

William