Stefan Gybas wrote:
josh buhl wrote:Here's the deal: I have Sun's j2sdk1.4.2_01 installed. That pretty much takes care of all the java dependencies, but since it's not a debian package, none of the debian java stuff knows about it. I don't want to install any of the packages that provide java2-runtime, since I've already got the real deal. However, any package that depends on java2-runtime or j2re1.4 for example refuses to install, although they would run fine if they would install themselves. It seems that installing the java-virtual-machine-dummy package should convince all other packages that their dependencies are covered. That's what it's there for.The latest libtomcat4-java package has this dependency removed (for different reasons) but this won't help you since all other Java library
Yes it will, because I have the *dummy* package java-virtual-machine-dummy installed. this satisfies those dependcies!
packages that libtomcat4-java depnds on still have a dependency on java2-runtime which can't be satisfied on your system.
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.
No I can't. It reports unmet dependencies, saying it depends either on java2-runtime, j2re1.4 or j2re1.3. See above.So how did you satisfy tomcat4's dependency on java-virtual-machine? You need to install some Debian package that provides j-v-m.
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.
You can use equivs for that. See README.Debian in java-common for details.
thanks for the tip, I'll have a look.
The dummy packages have been removed from unstable and should also be removed from testing. But this is not going to happen since it's the only package there that provides java2-runtime and the Debian archive maintainance scripts won't allow unresolved dependencies in testing.
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.
josh