Skip to content
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

Ambigous license #17

Open
AMDmi3 opened this issue Feb 20, 2015 · 3 comments
Open

Ambigous license #17

AMDmi3 opened this issue Feb 20, 2015 · 3 comments

Comments

@AMDmi3
Copy link

AMDmi3 commented Feb 20, 2015

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.

@indeyets
Copy link
Owner

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

@AMDmi3
Copy link
Author

AMDmi3 commented Feb 21, 2015

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.

@Daveawb
Copy link

Daveawb commented Nov 30, 2015

@AMDmi3 I do believe that you are a living being using this software, as such you shall be punished to the full extent of the law. ;-)

https://github.com/indeyets/syck/blob/master/COPYING

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants