-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add LICENSE #1
Comments
SDCC uses GPL2+LE (i.e, GPL 2 or later with liking exception) for its library. |
This repo is the programmer specific include files (i.e. calibration routines) and is not currently intended to be included with SDCC. But, your comment would apply to the pdk-includes repo: free-pdk/pdk-includes#5 |
Pull Request adding Copyright and LICENSE information: #2 |
I'm not sure if the old LGPL is the right choice for headers which are included in a linked program. I think GPL + LinkException is a better choice for this. |
Do you have a link that shows that as being a real thing? I couldn't find it on http://www.gnu.org/licenses, and it isn't directly listed on their exceptions page either: https://www.gnu.org/licenses/exceptions.html GitHub doesn't know about it: https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository SPDX doesn't directly list it (unless it is one of the deprecated ones): https://spdx.org/licenses/ Wikipedia isn't really all that clear, although they do list LGPL as being related: https://en.wikipedia.org/wiki/GPL_linking_exception Or, do we just list this as GPL 2.0 and include our own exception text (similar to what SDCC uses)? That feels a bit dirty to not use an 'official' license, but maybe it is ok? |
https://en.wikipedia.org/wiki/GPL_linking_exception In SDCC I only found this: => we need to ask @spth Linking Excpetion: |
But you use an official license. You just add an additional exception. |
Ok, here is a different PR with GPL v2 with Linking Exception: #3 |
Copyright and LICENSE information was merged via pull request #3 |
This repo need a clearly identified LICENSE so people know what can and cannot be done with it.
@freepdk, my preference for this is MIT, but these files have their roots from easy-pdk-programmer-software which is GPL v3. Are you ok with (re-)licensing these include files as MIT, or should we keep this one as GPL v3?
The text was updated successfully, but these errors were encountered: