Re: Large-scale java policy violations

[Adam Heath <doogie@debian.org>]

On Mon, 17 Sep 2001, Per Bothner wrote:

> Stefan Gybas wrote:
>
> > Basically yes, but IMHO this should be the decision of the local admin
> > and not of the package maintainer. How could he know ig his package
> > contains "standard" jars? This means that no package should automatically
> > put jars or symlinks there. This would be /etc/java/default-classpath/ in
> > my proposal.

update-jars --install /usr/share/java/<foo>.jar <foo>.jar \
	/usr/share/java/<foo>-<ver>.jar <priority>

This looks very much like update-alternatives, and in fact, it really is.
However, update-jars does one additional item.  It maintains reference counts.
When the reference count is >= 1, then the jar gets added to the default
classpath.  For speed, this default classpath is created in the file
/var/lib/java/def_classpath.

Additionally, /etc/java/classpath is conffile(and gets all the normal dpkg
treatment), which contains a reference to '@def_classpath@', which is replaced
at runtime, by the appropriate wrappers.

java-common should include the program update-jars, and, optionally,
get_sysclasspath, which combines /etc/java/classpath and
/var/lib/java/def_classpath.