Karl Trygve Kalleberg wrote:
>
> We are currently playing around with the following packaging scheme
> for java applications (0th draft):
>
> Each Java package will install its jar files into
> /usr/share/<packagename-slot>/lib/, instead of
> /usr/share/<packagename>/lib/
>
> There will still be a
> /usr/share/<packagename-slot>/package.env file, and it can contain
> more than just the CLASSPATH env variable.
>

So ... how does Java perform and handle monolithic CLASSPATHs?  These things
could become truly horendous in length!

Tom Veldhouse


--
[EMAIL PROTECTED] mailing list

Reply via email to