-
-
Notifications
You must be signed in to change notification settings - Fork 602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This project appears to be violating the GPLv2 #1264
Comments
Hey thanks @gotmax23, I've reached out to the author to see if that library can be released under another licensing option (he says he's willing on the github page). |
Thanks. I notched this while reviewing the package for Fedora. I also filed timtadh/lexmachine#39 but have not received a response thus far. |
Update: I'm looking at switching to a new lexer https://github.com/alecthomas/participle - which is MIT (and doesn't seem to have libs underneath it that are GPLv2). |
Also I still haven't received anything from Tim... |
Hi, I was out of office but I am writing you a email now with details. |
Feel free to CC me (gotmax@e.email). |
done. you should have received an email. |
Thanks @timtadh, @gotmax23 for looking into the licensing issue of your published libraries - however yq will be moving to a new lexer/parser (https://github.com/alecthomas/participle if you're interested). Participle is already licensed under MIT (which is permissive like BSD-3) it has an active community and it has some sophistication I'm interested in adding to yq expression language. This has been updated in v4.26.1 |
FYI as of github.com/timtadh/lexmachine v0.6.1 the licensing issue has been resolved. See timtadh/lexmachine#39 |
This package depends on github.com/timtadh/data-structures, which is licensed under the GPLv2. Thus, it seems that this package also needs to be licensed under the GPLv2 or at least be distributed under that license and have a copy of it in the repo (e.g. https://github.com/ansible/ansible-lint#licensing).
The text was updated successfully, but these errors were encountered: