2013/8/22 Björn Esser <bjoern.es...@gmail.com>: > Am Donnerstag, den 22.08.2013, 12:17 +0300 schrieb Vlad Niculae: >> Like Olivier said, libsvm and liblinear are heavily patched and >> scikit-learn wouldn't work with the upstream versions. > >> If bundling them is unacceptable, I guess maybe packaging our forks >> individually as libsvm-sklearn or something similar would be a >> solution, but I think it would be confusing. Also I am completely >> unaware of the constraints and of what Yaroslav is doing for Debian; >> by looking at his branch it looks like the libs are there. > > Can you please tell me a bit more about what / why these were modded? > If we cannot unbundle them, I need to have some further infos to get > some exception granted for them. :)
For the libsvm binding the main reason it to get both the sparse and dense memory layout for the input data. The upstream package only supports sparse input data and the dense variant lives in a 3rd party fork: http://www.csie.ntu.edu.tw/~cjlin/libsvmtools/#libsvm_for_dense_data For liblinear I am not sure anymore (I was not personally involved in those bindings). It's probably worth exploring with diff of the source folders. -- Olivier http://twitter.com/ogrisel - http://github.com/ogrisel ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Scikit-learn-general mailing list Scikit-learn-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
