On Fri, Sep 30, 2016 at 7:29 AM, wrote:
>
> Ian, can you please explain (briefly) what are requirements that the two
> licenses impose on the program ?
> Again thanks.
Both licenses are entirely readable, and I encourage you to read them.
Briefly, the GPLv2 requires that when you distribute the
On Friday, September 30, 2016 at 5:18:28 PM UTC+3, Ian Lance Taylor wrote:
>
> On Thu, Sep 29, 2016 at 1:12 AM, > wrote:
> > Hi,
> > May be OT, but:
> >
> > Can i translate some GPLv2 licensed C code to GO, and publish it under
> BSD
> > new license ?
> > Code comments are from original
On Thu, Sep 29, 2016 at 1:12 AM, wrote:
> Hi,
> May be OT, but:
>
> Can i translate some GPLv2 licensed C code to GO, and publish it under BSD
> new license ?
> Code comments are from original C code.
Despite some other replies here, I think you probably can, though you
can't copy the comments.
> Also, Can I in my BSD licensed GO project, link to GPLv2 library ?
You may link to the library via cgo if the author has given you
permission to do so. Usually this is done via a separate COPYING.LIB
file which contains the GNU LGPLv2 text in the library's repository
(the COPYING file still cont
Hi,
May be OT, but:
Can i translate some GPLv2 licensed C code to GO, and publish it under BSD
new license ?
Code comments are from original C code.
Also, Can I in my BSD licensed GO project, link to GPLv2 library ?
Regards,
Djadala
--
You received this message because you are subscribed to
