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

Behaviour of using unlicensed modules, kpm licenses #15

Closed
sebmck opened this issue Jan 19, 2016 · 2 comments
Closed

Behaviour of using unlicensed modules, kpm licenses #15

sebmck opened this issue Jan 19, 2016 · 2 comments
Assignees

Comments

@sebmck
Copy link
Contributor

sebmck commented Jan 19, 2016

What should the default behaviour be? A warning? Hard error? Prompt the user and make them type "yes"? Nothing?

We also possibly need the ability to specify bad licenses.

@vjeux
Copy link
Contributor

vjeux commented Feb 4, 2016

Right now license format is all over the place unfortunately on npm. Would be nice if kpm could enforce a consistent one. Bonus point if you can do kpm licenses and it would print a list of all the licenses from projects that you use so that you can put them in your legal section easily.

@sebmck sebmck changed the title Behaviour of using unlicensed modules Behaviour of using unlicensed modules, kpm licenses Jul 20, 2016
@sebmck sebmck self-assigned this Sep 15, 2016
@sebmck sebmck self-assigned this Sep 20, 2016
@sebmck
Copy link
Contributor Author

sebmck commented Oct 5, 2016

Going to close this and relegate enhancements to yarn licenses to separate issues.

@sebmck sebmck closed this as completed Oct 5, 2016
arcanis added a commit that referenced this issue Sep 13, 2018
Fixes an issue inside the pkg-tests helper
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants