Thank you for taking on this effort. I have been kicking around the
idea of uploading the development version of Weka to experimental, but
hadn't found time. This would make it available in the archive but
still keep the "book" version in stable. How would you feel about
taking your work and adding it as the weka3.7 branch to the
pkg-java/weka.git packaging repo?
P.S. I'm cross-posting this to debian-java for wider discussion.
On 03/18/2012 09:12 AM, Erich Schubert wrote:
> In case you are interested, I've prepared a Weka 3.7.5 package (i.e.
> current development version) at
> The move from 3.6 to 3.7 required some changes to the build process,
> as it was relying on a precompiled .jar for the package manager (which
> doesn't seem to work for me; also not with the official build). I
> managed to work around it by compiling it (from the .jar in .jar
> sources) in a first step, then compiling the main part of Weka.
> Anyway, in case you are updating the package to the development
> series, feel free to have a look at how I prepared it. On the other
> hand, of course, this may also change upstream in the meantime.
> Weka 3.7.5 exposes debian bug #664515 in java-wrappers, which sets the
> classpath to ":weka.jar". This classpath is interpreted as
> ".:weka.jar", causing Weka to scan the file system starting in the
> current folder (or when launched from the .desktop file, in the users
> home folder). When there is an infinite loop - e.g. in the .wine
> folder - this will prevent Weka from starting.
03-18-2012, 07:20 PM
Weka 3.7.5 package
As there are some issues with the 3.7 version:
- the new "package manager" seems non-working to me
- no PDF/LaTeX documentation, only Javadoc?
I do think that making a separate weka-dev package is sensible.
I'm not sure whether it is better to make it a weka3.7 branch or a
"weka-dev" branch (as in book + 0.1). I havn't been following weka for
long enough to tell. However, I do see that some people will want to
use the "book" release, while others might need the latest development
version (for the improved sparse support in Apriori e.g.).
When a new book release is out as 3.8, I figure the new dev will be e.g. 3.9?
I probably won't be using weka much, so I likely won't continuously
update it. I'm involved in teaching a KDD class in the summer term,
and for this I needed the 3.7 version. Building a package helps the
admins to install it throughout the computer pool (which is running
Ubuntu, but in particular Java packages should be very portable).
My main interest is the ELKI package, as I'm not doing much
classification but mostly outlier detection and clustering. In my own
experiments, ELKI was significantly faster even in k-means, which is
well integrated with Weka, too. But KDD also involves classification,
obviously, and I intend to use Weka for this in class.
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com
Archive: CAGKbab8nVLmco9SF6QjmiKztbjXnmsPwcX_mBcmODSBgNWg6i firstname.lastname@example.org">http://lists.debian.org/CAGKbab8nVLmco9SF6QjmiKztbjXnmsPwcX_mBcmODSBgNWg6i email@example.com