Triggered by a thoughtful observation from Matthias KURZ [0], we considered how the future package structure should be for packages containing java bytecodes (.jar or .class files). Please post objections to the standard we concluded on.
A java package contains bytecode files in %{l_prefix}/lib/<pkgname>
along with all its runtime resources.
The j2se package itself stays in %{l_prefix}/libexec/j2se due to its
platform specific code.
So for example in the instance /openpkg we have:
/openpkg/libexec/j2se
/openpkg/lib/ant
It is unclear if a new abstraction is needed along the lines of
the package perl-openpkg. If so it would be called java-openpkg.
The main question is how to coerce java bytecode to recognize
the redirected destination paths of any resource dependencies.
The existing java packages
ant
fop
j2ee
jboss
ditaa
tomcat
gallery
xalan (?)
saxon (?)
ganttproject
...do not yet conform to the above standard, but will be modified. They
are all EVAL class packages, and thus hopefully will not cause too many
problems when some of their paths change.
Regards,
Michael
--
Michael Schloh von Bennewitz <[EMAIL PROTECTED]>
Development Team, Operations Northern Europe
Cable & Wireless Telecommunications Services
Tel +49-89-92699-227, Fax +49-89-92699-808
pgpAI9S6tAa22.pgp
Description: PGP signature
