Bug#502851: [libsoprano4] Build sesame2 backend
Sune Vuorela wrote: But upstreams sources ship precompiled jars of java libraries not present in the archive. The primary jar is openrdf-sesame-2.1.2-onejar.jar which actually embeds a lot of other jars (java people apparantly like embedded code copies). Someone dug up that it is probably around this list of jars embedded: [very long list of jars] There has been a interesting discussion on ubuntu-devel regarding a related topic [1]. Apparently it is not always as easy as packaging all the different jars, as very often they break compatibitity between versions. So Java developers end up packaging up the exact, tested version of all the jars bundled up. So it is at least questionable, if packaging the myriad of different jars is actually leading up to a working solution and definitely would require lots of work, testing and time. Why not simply ship the precompiled sesame jar (in non-free) in the meantime? As nepomuk can easily fall back to other backends you'd not have to make a hard dependency on it. Cheers, Michael [1] https://lists.ubuntu.com/archives/ubuntu-devel/2009-January/027272.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#502851: [libsoprano4] Build sesame2 backend
block 502851 by 512396 thanks Michael Biebl wrote: Why not simply ship the precompiled sesame jar (in non-free) in the meantime? If we went that route we could put almost all of Debian, especially a lot of Java software, in non-free and just save a lot of work and compilation time... I think the time is better spent helping to package the software in question (ITP bug #512396), which should not be too complicated although there are many packages. From a cursory inspection, the Spring jars are not needed for the backend. Cheers, Marcus signature.asc Description: This is a digitally signed message part.
Bug#502851: [libsoprano4] Build sesame2 backend
Sune Vuorela wrote: On Monday 20 October 2008 11:41:16 Robert Wohlrab wrote: Package: libsoprano4 Version: 2.1+dfsg.1-1 Severity: wishlist I tried to use nepomukserver with kde and had to notice that it was extreme slow - different to what I experienced on other distributions. The problem is that it searches for /usr/share/soprano/plugins/*backend.desktop and can only find the redland backend. If you get someone to pacakge the myriad of java libraries needed by sesame, I guess we will happily somehow enable sesame backend. What is exactly needed for sesame? When compiling from source, all I had to do to enable the sesame backend is to point cmake to the java directory (I've set JAVA_HOME=/usr/lib/jvm/java-6-sun). That's all I needed to get the sesame2 backend compiled. How can I check if the sesame backend is working correctly? I haven't tried it, but maybe all you need is to build depend on openjdk and set JAVA_HOME approriately. Maybe not, I don't really know. I just thought I throw in my 2ยข. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#502851: [libsoprano4] Build sesame2 backend
On Wednesday 28 January 2009 06:13:20 Michael Biebl wrote: Sune Vuorela wrote: On Monday 20 October 2008 11:41:16 Robert Wohlrab wrote: Package: libsoprano4 Version: 2.1+dfsg.1-1 Severity: wishlist I tried to use nepomukserver with kde and had to notice that it was extreme slow - different to what I experienced on other distributions. The problem is that it searches for /usr/share/soprano/plugins/*backend.desktop and can only find the redland backend. If you get someone to pacakge the myriad of java libraries needed by sesame, I guess we will happily somehow enable sesame backend. What is exactly needed for sesame? When compiling from source, all I had to do to enable the sesame backend is to point cmake to the java directory (I've set JAVA_HOME=/usr/lib/jvm/java-6-sun). That's all I needed to get the sesame2 backend compiled. How can I check if the sesame backend is working correctly? That part is the easy part. But upstreams sources ship precompiled jars of java libraries not present in the archive. The primary jar is openrdf-sesame-2.1.2-onejar.jar which actually embeds a lot of other jars (java people apparantly like embedded code copies). Someone dug up that it is probably around this list of jars embedded: activation-1.1.jar aduna-appbase-core-3.1.jar aduna-appbase-logging-api-3.1.jar aduna-appbase-logging-file-3.1.jar aduna-appbase-webapp-base-core-3.1.jar aduna-commons-collections-2.0.jar aduna-commons-concurrent-2.0.jar aduna-commons-io-2.0.jar aduna-commons-iteration-2.0.jar aduna-commons-lang-2.0.jar aduna-commons-net-2.0.jar aduna-commons-platform-info-2.0.jar aduna-commons-text-2.0.jar aduna-commons-webapp-core-2.0.jar aduna-commons-xml-2.0.jar aopalliance-1.0.jar asm-1.5.3.jar cglib-2.1_3.jar commons-cli-1.1.jar commons-codec-1.2.jar commons-dbcp-1.2.2.jar commons-httpclient-3.1.jar commons-pool-1.3.jar jcl104-over-slf4j-1.5.0.jar jstl-1.1.2.jar logback-classic-0.9.9.jar logback-core-0.9.9.jar slf4j-api-1.5.0.jar slf4j-jdk14-1.5.0.jar spring-beans-2.5.1.jar spring-context-2.5.1.jar spring-context-support-2.5.1.jar spring-core-2.5.1.jar spring-web-2.5.1.jar spring-webmvc-2.5.1.jar standard-1.1.2.jar where like 2 of them are in the archive already. I haven't tried it, but maybe all you need is to build depend on openjdk and set JAVA_HOME approriately. Maybe not, I don't really know. when the jars is available, that's also what I expect to be done. /Sune -- How to log from the application from Excel? You either need to rename the jumper, or can't mount the space bar for debugging a FPU of a file. signature.asc Description: This is a digitally signed message part.
Bug#502851: [libsoprano4] Build sesame2 backend
Package: libsoprano4 Version: 2.1+dfsg.1-1 Severity: wishlist I tried to use nepomukserver with kde and had to notice that it was extreme slow - different to what I experienced on other distributions. The problem is that it searches for /usr/share/soprano/plugins/*backend.desktop and can only find the redland backend. Regards, Robert --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-1-amd64 Debian Release: lenny/sid 500 unstableftp.debian.org 500 unstabledebian.netcologne.de 1 experimentalftp.debian.org --- Package information. --- Depends (Version) | Installed =-+-== libc6 (= 2.7-1) | 2.7-15 libclucene0ldbl (= 0.9.20-1) | 0.9.20-3 libgcc1 (= 1:4.1.1) | 1:4.3.2-1 libqt4-dbus(= 4.4.0) | 4.4.3-1 libqt4-network (= 4.4.0) | 4.4.3-1 libqtcore4 (= 4.4.0) | 4.4.3-1 libraptor1(= 1.4.16) | 1.4.18-1 librdf0(= 1.0.6) | 1.0.8-1 libstdc++6 (= 4.1.1) | 4.3.2-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502851: [libsoprano4] Build sesame2 backend
On Monday 20 October 2008 11:41:16 Robert Wohlrab wrote: Package: libsoprano4 Version: 2.1+dfsg.1-1 Severity: wishlist I tried to use nepomukserver with kde and had to notice that it was extreme slow - different to what I experienced on other distributions. The problem is that it searches for /usr/share/soprano/plugins/*backend.desktop and can only find the redland backend. If you get someone to pacakge the myriad of java libraries needed by sesame, I guess we will happily somehow enable sesame backend. /Sune -- How to click on the directory? You neither have to forward from the level-94 mouse of the IRC display over a system, nor should ever receive from a prompt but from MkLinux you must get access over a pointer for saving from the MIDI DirectGL URL. signature.asc Description: This is a digitally signed message part.
