Library dependencies

[Stefan Gybas]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig85A9EFA3A2E11D288D1C9DE2
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi!

As you probably know, a lot of our library packages won't move to 
testing because their dependencies can't be fulfiled with packages in 
Debian. However, most (if not all) of them work with Kaffe or SableVM, 
e.g. tomcat4 and all its library dependecies work with the latest Kaffe 
versions.

I have changed the dependency of libant1.6-java to "classpath-common | 
java1-runtime | java2-runtime" in the latest package. I think we should 
change all library dependencies to either

classpath-common | java1-runtime | java2-runtime

(if the library only requires JDK 1.1 core classes) or

classpath-common | java2-runtime

(of the library requires JDK 1.2+ core classes). Of course, dependencies 
on additional libraries must also be added.

Since both Kaffe and SableVM are more or less based on GNU Classpath we 
can assume thet the library works with Classpath's core classes if an 
application that uses this library works with either Kaffe or SableVM. 
The Java Policy only requires a dependency on the runtime classes - and 
these are well provided by /usr/share/classpath/glibj.zip from 
classpath-common now.

What do you think?

Stefan

--------------enig85A9EFA3A2E11D288D1C9DE2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA0uW/CdoSgNrrJGsRAqcNAJwPDzUKoNdxKlz2IWB0W1ChLmYplgCfTriS
hCyHh3I26OkcKm9UCUVwp7U=
=uE8w
-----END PGP SIGNATURE-----

--------------enig85A9EFA3A2E11D288D1C9DE2--