Jan Schulz wrote:
So what do you suggests as a alternative?Stay with the for i in $LIST_OF_ALL_KNOWN_JAVA_WHICH_WILL_WORK ; do... done and having a Depends like this: jsdk1.3 | jsdk1.4 |jsdk1.4-bd | j2sdk1.4-sun | kaffe (>..)|... (sun, bd and ibm should be from mpkg-j2sdk) Just imagine additional 1.5, 1.6 and so on...
You may have to do that. If you don't have a VM that has been *tested* with the package you're trying to install, then you don't know if you can satisfy the dependency. For convenience, you can say (I don't know the appropriate syntax): jdk version >= 1.2 | gcj version >= 3.3 | kaffe version >= ??? but that is no guarantee. A later version of JDK may add more methods to an interface (Sun has been known to do this), and if your package has a class that implements the interface, it will break. Plus of course people do add bugs. You can also "java-compatible-with-jdk1.3" but no Free JVM are likely to satisfy such a constraint anytime soon. (compilatible-with-jdk1.1 is getting close, though!) -- --Per Bothner per@bothner.com http://per.bothner.com/