You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
COPYING file says that syck is distributed under BSD license, however MIT license text is listed instead (see https://en.wikipedia.org/wiki/BSD_licenses, https://en.wikipedia.org/wiki/MIT_License). Though license terms are similar if not equal, it'd be nice to clarify which specific license is used. I, as package maintainer, am quite confused which license I should specify in the package metadata.
The text was updated successfully, but these errors were encountered:
I'm not the original author, so do not feel to be in position to change the license (even if it is ambiguous). also, syck barely should be packaged these days. It is seriously outdated. libyaml is a much better choice
I'm not asking to change the license, I just ask it to clarify it - if it's MIT, the text should say it's MIT. Maybe you have original author contacts so he can approve this change?
syck barely should be packaged these days
I'm just maintaining legacy ports. It may still be used by someone, however it's true that in FreeBSD ports collection the only consumers it has are its python, php and perl bindings.
COPYING file says that syck is distributed under BSD license, however MIT license text is listed instead (see https://en.wikipedia.org/wiki/BSD_licenses, https://en.wikipedia.org/wiki/MIT_License). Though license terms are similar if not equal, it'd be nice to clarify which specific license is used. I, as package maintainer, am quite confused which license I should specify in the package metadata.
The text was updated successfully, but these errors were encountered: