Hi Martin,
Martin Kittel wrote:
Hi Wolfgang,
Well, all free runtimes in debian are capable of running JDBC drivers. So
there is no point to exclude the other runtimes. If it works with
java-gcj-compat then it works with all the others given by the virtual
package java1-runtime e.g. kaffe, jamvm, sablevm. java-gcj-compat and
the other free runtimes share identical classpath library.
While kaffe seems to be ok, sablevm for example is unable to even
connect to a database when running the JDBC driver's tests... But maybe
that is not the issue here.
jamvm will work also, but you are right sablevm is really a problem atm.
Its too outdated and not really maintained these days. I myself just
reassign bug reports related to execution of a package on sablevm to
the sablevm package.
Although the free runtimes currently do not provide java2-runtime, they
are definitly mature enough for the aspect of JDBC. Its for the sake of
a not yet complete and 100% compatible swing library which makes them
not a 100% java2-runtime.
Ok, I will add the java1-runtime dependency, but if people start
complaining about their JDBC drivers not working I will probably remove
it again...
Thats perfectly your right - however I would recommend people first to
switch to a uptodate free vm and reassign the bug to sablevm.
BTW, whats the case with libsapdbc7.5.01-java ? It there a reason to keep
this package around ?
No, I need to find out how to have it removed now that libsapdbc-java is
in testing.
You just need to file a bug against ftp.debian.org asking for removal
of source and binary from the archive (unstable) and wait.
An explanation that it is superceeded by .... would be good.
Thanks,
Wolfgang
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
