Matthias Klose wrote:
>> If I follow the instructions for "Local installation" [2] which keeping
>> Debian Policy [3] in mind I then can do the following (to simulate
>
> local installations should never install directly into /usr, always in
> /usr/local. I think the Debian packaging guidelines a
Tom Marble writes:
> Juergen Kreileder wrote:
> > Tom Marble wrote:
> >> Current Debian Java Policy [1] in section "Chapter 2.1: Virtual Machines"
> >> stipulates "If a virtual machine supports native code, it must include
> >> the
> >> directory /usr/lib/jni in its search path for these dynamic li
Tom Marble <[EMAIL PROTECTED]> writes:
> And, we know already from Debian Java Policy and existing Java
> applications in Debian that a launcher script will be required in
> /usr/bin *anyway*
In that case your alternative looks good to me.
Juergen
--
Juergen Kreileder, Blackdown Java-
Juergen Kreileder wrote:
> Tom Marble wrote:
>> Current Debian Java Policy [1] in section "Chapter 2.1: Virtual Machines"
>> stipulates "If a virtual machine supports native code, it must include
>> the
>> directory /usr/lib/jni in its search path for these dynamic libraries."
>
> JVMs should not
Hi Tom,
Tom Marble wrote:
All:
Current Debian Java Policy [1] in section "Chapter 2.1: Virtual Machines"
stipulates "If a virtual machine supports native code, it must include the
directory /usr/lib/jni in its search path for these dynamic libraries."
There is no rationale given for this polic
All:
Current Debian Java Policy [1] in section "Chapter 2.1: Virtual Machines"
stipulates "If a virtual machine supports native code, it must include the
directory /usr/lib/jni in its search path for these dynamic libraries."
There is no rationale given for this policy choice and I fail to
see th
6 matches
Mail list logo
