Re: additions to java-policy

["T. Alexander Popiel" <popiel@wolfskeep.com>]

In message:  <3F2572FA.9050802@provective.de>
             Stefan Gybas <sgybas@provective.de> writes:
>
>Should Java programs or libraries that use a versioned JAR from another 
>Java library have a versioned package dependency on this libraray? E.g. 
>if I use the current /usr/share/java/xalan-2.5.0.jar in my package how 
>should my dependency look?
>
>1. no dependency on libxalan2-java (it's not required by the Java
>    policy)
>2. libxalan2-java
>3. libxalan2-java (= 2.5.0-1)
>4. libxalan2-java (>= 2.5.0)
>5. libxalan2-java (>= 2.5.0), libxalan2-java (<< 2.5.1)
>6. libxalan2-java (>= 2.5.0), libxalan2-java (<< 2.5.0.1)
>7. something else

I'd tend to go with #5, until the version number is formally moved
into the package name (to allow multiple versions to be installed
concurrently).

- Alex