[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [PROPOSAL] New Virtual Packages and way to handle Classpath



Hallo Dalibor,

* Dalibor Topic wrote:
>> Currently you forbit this, as you only know where the BD package put
>> their java and so it will break if you have sun-java packaged
>> (mpkg-j2sdk) and instaleld with that name.
>Can't the maintainers of Blackdown Java and mpkg-j2sdk resolve this naming
>issue among themselves? ;)

They should before mpkg-j2sdk enters debian...

>> I much for this, but it will need 'protection', so that this system
>> prevents to mistake kaffe for a sun compatible JVM-1.4.
>Could you elaborate on this one, as in give an example where kaffe can be
>mistaken for Sun's JVM 1.4 why such protection is needed?

/usr/bin/java -> Currently it is the default way to access java and it
can be provided by sablevm, kaffe, gcj, BD packages or mpkg-j2sdk made
packages:

jan@snoopy:~/debian/RPM/SOURCES$ update-alternatives --list java
/usr/lib/j2sdk1.4/bin/java
/usr/bin/gij-wrapper-3.0
/usr/lib/kaffe/bin/java
/usr/lib/j2se/1.4/bin/java
/usr/lib/j2se/1.3/bin/java
/usr/lib/j2sdk1.4-bd/bin/java

As it is know to be that 'unprotected', every package sonly uses it as
a fallback after consulting JAVA_HOME.

jan
-- 
Jan Schulz                     jasc@gmx.net
     "Wer nicht fragt, bleibt dumm."



Reply to: