Bug#227587: [PROPOSAL] Java library dependencies
Ben Burton wrote:
And this is my core problem with your proposal. You want to remove
j2/1-runtime, but you offer nothing whatsoever to replace it.
No, I don't. Java applications must still depend on the required
java*-runtime virtual packages, I just want this dependency removed for
library packages.
With your proposal, there is no guarantee that the correct core classes
will even be installed, let alone used.
Wrong. The application packages depend on the core classes that are
known to work and its wrapper script makes sure that they are used. Take
for example the tomcat4 package.
Jan's proposal addresses these issues as I mentioned before. But in the
meantime, I'd prefer to keep j1/2-runtime since this at least gives
users half a chance.
I've read Jan's proposal yesterday (but not the following discussion
with Dalibor and others, so I won't comment yet) and I don't see how his
proposal solves this problem. AFAICS his proposal simply removes the
java*-runtime virtual package altogether.
Um, surely the library packager should be the once to decide in what
circumstances the library will work? You'd rather push the burden from
one library packager to all users of that library (including end users
writing custom projects against that library)?
No, I push it to maintainers of Java applications which use the library.
As I mentioned in a previous mail, *building* a library against a set of
core classes gives a fairly good indication of whether the library
should work with those core classes.
Definietly no: For example classpath includes some of the Swing API
(just method stubs in some cases) and but is unable to run Swing
applications.
> Building (unlike running) *does*
run through all possible paths through the code,
Wrong, it just runs through the method signatures.
and since the only
difference between runtimes is (in theory) which classes are available
(not what they actually do), then this should give a fairly decent
result.
Also wrong. But since the latest sablevm package now provies
java2-runtime, my whole proposal is superfluous: sablevm will be
installed to satisfy the java2-runtime dependency if you don't already
have Blackdown packages installed and applications like tomcat4 will
simply not start. That's also a way to solve a problem...
Stefan
Reply to: