Be more explicit about the GPL dependency, and why it still works
TripleWhy opened this issue · 5 comments
Description
This library, or at least the NuGet package has a dependency to StrictEmit, which is GPLv3 licensed. Are you actually sure that you can release AdvanceDLSupport as LGPL in that case?
Yes. I am the author of that library as well, and I've granted myself a product-specific LGPL-compatible license of StrictEmit to ADL :P
I see, thanks for the response. But should that not be noted somewhere then? Because If I want to use ADL, or another library that depends on ADL, I will have to distribute a copy of StrictEmit as well.
Also note that VS makes me accept the GPL when I try to install ADL or something dependent on it from NuGet.
This actually sparked a discussion in the Firwood official Discord; Nihlus said he's going to add a license grant saying that if you only use ADL (and not use StrictEmit directly,) you can use ADL. If you wish to use ADL in a non-GPL project, you'll have to get in touch with Nihlus to negotiate a similar grant for your project.
TL;DR: There's gonna be a funky license that lets you use StrictEmit through ADL.
@TripleWhy Ah, I was not aware that VS did that. As Dylan says, I'll be looking at being more explicit about this.
I've added a license notice, and I figured out a way to make the StrictEmit dependency non-transitive (that is, projects referencing ADL will not automatically reference StrictEmit themselves).
https://github.com/Firwood-Software/AdvanceDLSupport/blob/master/StrictEmit-LICENSE.md
I'll consider the issue closed for now :)