-
Notifications
You must be signed in to change notification settings - Fork 465
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
Clarify LICENSE (BSD or MIT) #293
Comments
koobs
added a commit
to freebsd/freebsd-ports
that referenced
this issue
Feb 16, 2014
- Enable AUTOPLIST support, delete pkg-plist - Update LICENSE (BSD -> MIT) [1] - Specify min django version in *_DEPENDS - Remove GH_TAGNAME, defaults to DISTVERSION already - Remove setup.py patch, no longer necessary - Sort USE section [1] django-mptt/django-mptt#293 Approved by: portmgr (blanket)
Good spotting, I hadn't noticed this. Looks like this bug has actually been around right since the start (@15958bfb9c357efefe6bef39288a1ff7c821936b) and you're the first to have actually read the license enough to notice ;) It's definitely a verbatim MIT license, I'll update the classifier to suit. |
My pleasure Craig, thanks for the quick resolve :) |
svmhdvn
pushed a commit
to svmhdvn/freebsd-ports
that referenced
this issue
Jan 10, 2024
- Enable AUTOPLIST support, delete pkg-plist - Update LICENSE (BSD -> MIT) [1] - Specify min django version in *_DEPENDS - Remove GH_TAGNAME, defaults to DISTVERSION already - Remove setup.py patch, no longer necessary - Sort USE section [1] django-mptt/django-mptt#293 Approved by: portmgr (blanket)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current LICENSE definition looks mostly like either the "Previous BSD" license or MIT license:
https://en.wikipedia.org/wiki/BSD_licenses#Previous_license
http://opensource.org/licenses/MIT
.. but none of:
as specified in the PyPi Trove classification in setup.py:
https://github.com/django-mptt/django-mptt/blob/master/setup.py#L36
Please clarify the LICENSE file with one of the above verbatim, and update the trove classification to suit.
The text was updated successfully, but these errors were encountered: