It seems people have a hard time understanding the implications of licenses, so I have written a something to help with that.
It seems people have a hard time understanding the implications of licenses, so I have written a something to help with that.
The license seems to be targeted towards languages like C/C++. On the other hand, languages like Go do a lot of static linking, so it may be impossible to comply with this license in Go.
MPL may be a good alternative here.
Nah, so long as the folks using the LGPL code provide everything necessary to use a different version of the LGPL part of the code, it doesn’t actually matter if it’s static or dynamic.
http://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic
Yeah, I think this is the hard part with Go. I’ve never seen anyone do anything with objects in Go. Everything is compiled into 1 binary, often statically linked. I’m not sure it’s possible to build a Go binary by using object files.