Package: debian-policy
Version: 3.8.4.0
Severity: wishlist
Justification: Policy ยง3.6
X-Debbugs-CC: debian-de...@lists.debian.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
As of today[1], the Java Policy retired the use of the virtual packages
mentioned
in the subject line, which brings the Java Policy closer to the actual practices
used by the Java Team.
The replacement guide for the packages are as described below. Please note that
these are guide lines for the average case. If a package does not fit "in",
feel free to contact the Java Team (debian-j...@l.d.o) about it.
[java-virtual-machine]
- none if already depending(or recommending/...) on a java runtime[2].
- An alternative list of java runtimes (see [2]) otherwise.
[java{,2}-compiler]
- default-jdk. If used in an alternative in Build-Depends{,-Indep} then pick
one of the options (The Java Team recommends default-jdk).
In case you change your Build-Depends{,-Indep} to include default-jdk, you
should update JAVA_HOME to /usr/lib/jvm/default-java if your build system
(e.g. ant) uses it.
Please do *not* switch to default-jdk-builddep without consulting the Java Team
first. On most architectures default-jdk-builddep will pull *two* full Java
Development Environments.
There is a reason for "insanity"; if you are interested then get in contact
with
the Java Team.
Thank you in advance,
~Niels
NB: I am subscribed to debian-de...@l.d.o, but not debian-pol...@l.d.o; please
CC
me accordingly.
[1] http://packages.qa.debian.org/j/java-common/news/20100419T071712Z.html
[2] e.g. one of these default-jre, default-jre-headless, java1-runtime,
java2-runtime
If you use indiviual JVMs (e.g. gij or gcj) it may be worth replacing them
with
default-jre{,-headless} plus alternatives.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkvMoaIACgkQVCqoiq1YlqyQkwCfSvVWBsnto4SlIeGuitjsOIBd
gZ0AnilwrFjEfUNB2LVf1uoaai5YJlYr
=hAv9
-----END PGP SIGNATURE-----
