Re: Bug#228878: java-virtual-machine-dummy and java2-runtime dependencies
josh buhl wrote:
no they don't. some, like tomcat4, have an "or" type dependency on
java-virtual-machine, so the dummy package takes care of this. the only
two java packages giving me a headache right now are libtomcat4-java and
libcommons-beanutils-java, both of which insist on installing
java2-runtime and don't acknowledge java-virtual-machine.
Funny, these two are the only ones that follow the Debian Java Policy.
All others either just depend on java-common or on java-virtual-machine,
both is wrong accoding to the Java Policy.
I find it very interesting that there are no bugs are filed against them
so I guess nobody cares. This also shows me that not following the Java
Policy works better in the real world.
I guess you didn't read my report closely enough: There's a package
called java-virtual-machine-dummy which provides java-virtual-machine
which you can install if you have some non-debian jvm installed, like
sun's j2sdk.
This package should also provide java*-runtime. Which other dummy
package should do this otherwise?
well, this is always going to be a problem. i don't see how you can
remove the dummy packages without causing headaches for everybody who
wants to use Sun's j2sdk or j2re (or any other non debian jvm or
whatever). you need a dummy package to tell other debian packages that
it's alright if they install themselves and not to worry about it.
Believe me, I know. I get a lot of bug reports and personal mails about
this.
Stefan
Reply to: