Closed apetro closed 7 years ago
Thank you for pointing this out. But, I think it would be better to rename the lgpl.txt to LICENSE rather than having two files with the same or similar content. I can do that (the build procedures will also need to be updated to include LICENSE file instead of lgpl.txt).
Does not change the licensing of this repo, just more clearly communicates existing licensing.
Same LGPLv3 license and text as existing
lgpl.txt
. Adding as LICENSE file should get e.g. GitHub's license metadata detection to label the repo as LGPL.