[09:50] <vil> doko: ping
[10:22] <doko> vil:pong
[10:24] <vil> looking at the eclipse-cdt build traces, i found that we do not have eclipse-3.2.1 for sparc
[10:24] <vil> some platform dependent sources for sparc are missing in the upstream
[10:25] <vil> is it ok, that eclipse-cdt-3.1.1 will be missing for sparc too?
[10:30] <doko> vil: sure, or else fix it to build on sparc =)
[10:30] <vil> right, veeeery funny :)
[10:35] <vil> doko: ademan had also nice idea that update-java-alternatives will make eclipse use the prefered VM. i guess that the update-java-alternatives can reorder the /etc/eclipse/java_home file.
[10:35] <vil> do you agree?
[10:38] <doko> vil: I don't know what to agree to ...
[10:40] <vil> doko: just asking if you consider this change useful
[10:42] <vil> update-java-alternatives comes from java-common, which comes from main. so i can only make some diff, but the upload would be yours
[10:48] <doko> vil: no, we are not allowed to change the config file of another package
[10:49] <vil> doko: ok, so is there other way to make eclipse use JVM selected by update-java-alternatives?
[10:50] <doko> vil: yes, use /usr/bin/java
[10:50] <doko> but then you have to check that this version is not configured to point to a vm which doesn't run eclipse
[10:52] <vil> doko: understood
[10:53] <vil> maybe /usr/bin/java isn't optimal because the JVM for eclipse is specified by a -vm param rather than the java binary
[10:53] <vil> anyway, modifying the eclipse startup script sounds like the prefered way
[10:54] <vil> thx for consultation
[10:58] <doko> np
[10:58] <doko> btw, will you be at fosdem?
[11:02] <vil> doko: unfortunately not, i will be at a trip in the states at that time.
[11:03] <vil> i have seen some people discussing it at debian-java
[02:02] <vil> doko: still cannot build it at ia64, could you please have a look at http://librarian.launchpad.net/5619195/buildlog_ubuntu-feisty-ia64.eclipse-cdt_3.1.1-0ubuntu2_FAILEDTOBUILD.txt.gz
[02:04] <doko> vil: don't know, but that is wrong: /usr/lib/jvm/java-gcj/bin/java -Dgnu.gcj.precompiled.db.path=/var/lib/gcj-4.0/classmap.db -cp /usr/lib/eclipse/startup.jar \
[02:04] <doko> the 4.0
[02:05] <vil> doko: oops
[02:05] <vil> what is this classmap.db used for?
[02:08] <doko> it's a lookup table which binary to load for which .class file
[02:09] <vil> doko: i can upload yet another version fixing this but it does not seem to matter so much as i386, amd64 and powerpc builds succeeded
[02:10] <vil> don't you know of any ia64 machine where i could experiment with the build. that log is not really very useful
[02:12] <doko> vil: no, currently not
[02:15] <vil> doko: do you consider s/4.0/4.1 worth making yet another package version?
[02:16] <vil> i understand it like that it fails to find the precompiled natives only while compiling  the eclipse-cdt. that can be acceptable
[02:18] <doko> exactly, that's not the primary failure
[03:38] <vil> doko: yesterday you mentioned that we need to fix eclipse. what is the problem?
[03:39] <doko> vil: it's the outstanding SRU, uploaded today.
[03:53] <vil> doko: i give up, didn't find it anywhere. where was it uploaded?
[03:54] <doko> vil: oh, it's still in the queue, needs manual approval
[03:55] <vil> doko: ok, will check that later. there is a long waiting problem with subclipse / subversion in eclipse. don't you know anything about it?
[03:57] <doko> sorry, no
[03:58] <vil> doko: and finally
[03:59] <vil> can update-java-alternatives set JAVA_HOME system-wide?
[03:59] <doko> no
[03:59] <vil> JAVA_HOME is a common java variable and is utilized by plenty of others apps
[04:00] <doko> no debian application should rely on environment variables
[04:00] <vil> doko: this channel is called #ubuntu-java ;)
[04:00] <vil> np, i will find something else
[04:01] <doko> maybe, but adding something like this makes packages very incompatible ...
[09:01] <vil> doko: back to the eclipse and jvm
[09:01] <vil> do we need to check if the jvm is eclipse compatible?
[09:08] <vil> can the /usr/bin/java be set to a jvm that cannot run eclipse?
[09:10] <doko> kaffe, cacao, sablevm?
[09:13] <vil> honestly, i don't know them
[09:14] <vil> i was just wondering, if we can get rid of all the -vm -install -startup paramters in the /usr/bin/eclipse script
[09:17] <vil> doko: does any of kaffe, cacao, sablevm a record in the java-alternatives?
[09:18] <vil> in any case -install -startup seem redundant to me
[09:18] <doko> yes, they provide alternatives
[09:19] <vil> doko: i just tried to install sablevm and kaffe packages and the only alternatives i get are gcj and sun
[09:20] <doko> update-alternatives, not update-java-alternatives
[09:24] <vil> doko: ok, get it, we could check if /usr/bin/java is listed in /etc/eclipse/java_home
[09:24] <vil> btw. /usr/lib/jvm/java-6-sun is still not listed there
[09:26] <doko> vil: I didn't do an upload after the sun-java6 upload ;p
[09:35] <vil> doko: i will give you rest for today. have a nice evening
[09:35] <doko> heh, np