This would only be true if *derivatives* were specified. Go links everything static by default, so in *very* broad terms, the binaries are derivative of the stdlib in the distributed go compiler package. I think really the proper way to look at this is this exact subject is simply not mentioned, only distantly implied in a specific way of interpreting it, and it would not be open-and-shut in a law court.
Since the compiler produces static binaries by default, I think it should be explicated in the licence that embedding the unmodified binary objects does not qualify as 'derivation' and licence terms do not apply. It's no problem right now, but it seems to me the licence does give wiggle room to Google to play silly buggers on the margins of this. And on the other side, what about when I build the binaries of stdlib using gcc or some other mostly complete not-google implementation? Seems to me the licence would cover this, and thus require the distribution of that licence. So I'm just going to quietly suggest that the licence needs to be revised. On Wednesday, 27 February 2019 15:46:23 UTC+1, Manlio Perillo wrote: > > > On Wednesday, February 27, 2019 at 2:58:40 AM UTC+1, Space A. wrote: >> >> Mentioned license doesn't cover binaries produced by compiler, "binary >> form" there means go tools themselves, and stdlib only when redistributed >> separately as a whole in binary form. When stdlib is used to compile >> regular binary, it's not "redistributed", and there are no restrictions or >> special requirements at all. >> >> Correct answer: if you are using only stdlib and Go compiler to compile a >> binary - there are no requirements. If you are using 3rd parties libs / >> binaries / sources - read their licenses. >> >> > No, **there is** a requirement: > > Redistributions in binary form must reproduce the above copyright notice, > this list of conditions and the following disclaimer in the documentation > and/or other materials provided with the distribution. > > This requirement does not only apply when you redistribute a (possibly) > modified version of the Go compiler, but also to the standard library. > So you have to link the Go License in your documentation, when you > redistribuite a Go program, since **every** Go program implicitly imports > the runtime package. > > But I'm not really sure. > > > Manlio Perillo > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
