Closed iffy closed 4 years ago
Thanks for the question @iffy. Both solutions are possible in Nim (make a build object available to users or link dynamically instead of statically) but I'd be happy to switch to the more popular MPL-2.0 that allows static linking if @alaviss @enthus1ast @TimseineLPs are OK with it.
I'm ok with it.
It's an OK from me also.
@enthus1ast ping -- Are you okay re-licensing nim-libsodium
as MPL-2.0? I'm getting very close to releasing my software, and the current licensing will hold me back.
@iffy sure i'm ok (just asking why not MIT?)
I'd be fine with MIT, ISC (to match libsodium) or MPL-2.0. @FedericoCeratto suggested MPL-2.0 (and that works for me).
The license has been updated.
@enthus1ast MPL 2.0 protects developers and users from patent trolling. It does not address other problems, but it's better than nothing.
Libsodium is licensed with ISC, but I just noticed that this library is licensed with LGPLv3, so I'm trying to figure out what my obligations are.
As I understand it, LGPLv3 requires me to provide the source of nim-libsodium and also either:
I'm not sure how to comply with the LGPLv3 license in a commercial, closed-source project. Any ideas? Would you be willing to change to ISC to match Libsodium? I'm happy to direct users here to the source and will continue to contribute patches back.
Thanks!