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
jav
Stefan Gybas wrote:
You can use equivs for that. See README.Debian in java-common for
details.
very nice. i see that this does take care of the problem, but how are
you going to get the user to know/do this, since when installing, all he
sees is a error message reporting missing dependencies. th
Stefan Gybas wrote:
You can use equivs for that. See README.Debian in java-common for
details.
very nice. i see that this does take care of the problem, but how are
you going to get the user to know/do this, since when installing, all he
sees is a error message reporting missing dependencies. th
Hi Josh,
josh buhl wrote:
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
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
5 matches
Mail list logo
