5 ms·
This looks like a great effort and I am looking forward to trying it out. I am a bit confused by the choice of the LGPL 3.0 license. It requires one to dynamic
by bojanz 3y ago
This looks like a great effort and I am looking forward to trying it out.
I am a bit confused by the choice of the LGPL 3.0 license. It requires one to dynamically link the library to avoid GPL's virality, but in a language like Go that statically links everything, it becomes impossible to satisfy the requirements of the license, unless we ignore what it says and focus just on its spirit. I see that was discussed previously by the community in posts such as these [1][2][3]
I am assuming that bgentry and brandur have strong thoughts on the topic since they avoided the default Go license choice of BSD/MIT, so I'd love to hear more.
[1] https://www.makeworld.space/2021/01/lgpl_go.html https://www.makeworld.space/2021/01/lgpl_go.html
[2] https://golang-nuts.narkive.com/41XkIlzJ/go-lgpl-and-static-linking-pitfalls https://golang-nuts.narkive.com/41XkIlzJ/go-lgpl-and-static-...
[3] https://softwareengineering.stackexchange.com/questions/179084/is-there-a-modified-lgpl-license-that-allows-static-linking https://softwareengineering.stackexchange.com/questions/1790...
- deleted 3y ago[deleted]
- bgentry 3y agoHi bojanz, to be honest we were not well informed enough on the licensing nuances. I appreciate you sharing these links, please tune into this GitHub issue where we'll give updates soon and make sure any ambiguity is resolved. https://github.com/riverqueue/river/issues/47 https://github.com/riverqueue/river/issues/47