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

remove weka dependency #65

Open
mssammon opened this issue May 3, 2016 · 6 comments
Open

remove weka dependency #65

mssammon opened this issue May 3, 2016 · 6 comments

Comments

@mssammon
Copy link
Contributor

mssammon commented May 3, 2016

weka has GPL2 license, not compatible with academic use. Can we remove, or at least separate, the Weka dependency?

@christos-c
Copy link
Member

Weka is used for SVM I think but also has a very specific version o thef java_cup dependency.

@mssammon
Copy link
Contributor Author

mssammon commented May 3, 2016

not using liblinear for svm?
weka is the source of the java_cup lbjava needs (i.e. there isn't an alternative)?

@danyaljj
Copy link
Member

danyaljj commented May 3, 2016

As far as I know it is not used directly in any of the libraries. There's only one wrapper to call its classifiers.

On another line, what issue does it create? I mean, why can't we say "if you use any component which uses external tools you're subject to their license"?

@mssammon
Copy link
Contributor Author

mssammon commented May 3, 2016

That might be a way out but I suspect it would be subject to serious debate. The simplest way to resolve it is to avoid the dependency. Here's one take: http://blog.milkingthegnu.org/2008/04/gpl-for-dummies.html -- and the bottom line is the intent of the creator in using GPL in the first place.

@danyaljj
Copy link
Member

danyaljj commented May 3, 2016

Well I don't think "avoiding dependency" is possible. In fact recently Dan's undergrad student was working to add more external libraries (e.g. for neural networks). External dependencies are unavoidable.

@mssammon
Copy link
Contributor Author

mssammon commented May 3, 2016

We can use any dependency that uses a LGPL-like license, so it's not a blanket avoidance.

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

3 participants