-
Notifications
You must be signed in to change notification settings - Fork 19
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
Feature: Please consider "Zope Public License" #43
Comments
As for the alternative, just saw the --ignore-licenses option: However, following settings do not seem to work
Exit code is still 1 and licenses are shown as not compatible:
|
@fhg-isi you could try to use the
|
Hopefully the ignore-licenses has been fixed. But yeah the ignore-packages is another workaround you may want to use. Also depending on how you use licensecheck you may just want to make a note when using it / for the development team? Of course this is a different story for CICD. I'll be sure to investigate this further and hopefully can confirm a fix for that behaviour Not sure when I'll be supporting Zope public license yet, there are a few bits of refactoring I'd like to do to support unknown compatibility states and improve compatibility management |
Nope. But ignoring the individual package(s) that use that license worked as a workaround. |
Is your feature request related to a problem? Please describe
I use the library waitress, having a "Zope Public License":
https://github.com/Pylons/waitress
https://github.com/Pylons/waitress/blob/main/LICENSE.txt
licensecheck yields
WARN: 'ZOPE PUBLIC LICENSE' License not identified so falling back to NO_LICENSE
Describe the solution you'd like
Consider the license
Describe alternatives you've considered
Support of a whitelist, so that I can alter the behavior of licensecheck by configuration.
The text was updated successfully, but these errors were encountered: