> However, I don't see this change going in Squeeze. If you are OK, I will
> upload your modification as soon as Squeeze is out (and also in Ubuntu).
> This will allow us some deeper testing and potential side effects.
>
> How does it sound ?
> Sylvestre
Sounds great - I didn't expect it to get into squeeze/ubuntu and think
it needs testing before making into a stable release.
I don't know if you saw this:
On Wed, Nov 17, 2010 at 11:24 AM, Matthias Klose
<email address hidden> wrote:
>> On Sat, Nov 13, 2010 at 10:52 AM, Scott Howard<email address hidden> wrote:
>>> I also don't
>>> know if a user setting LD_LIBRARY_PATH on their own overwrites our
>>> java.library.path
>
> this is incomplete; only works if the jvm is called by the java binary.
>
I'm seeking some more help from java people at sun one last time
before we might have to just say that an incomplete solution might be
the only policy-compliant [1] solution for a non-free package. Please,
if anyone knows of a better way let us know (the joys of non-free
packages: features can be undocumented and a mystery!). The best fix
is to use open-jdk, which I've been suggesting to users.
> However, I don't see this change going in Squeeze. If you are OK, I will
> upload your modification as soon as Squeeze is out (and also in Ubuntu).
> This will allow us some deeper testing and potential side effects.
>
> How does it sound ?
> Sylvestre
Sounds great - I didn't expect it to get into squeeze/ubuntu and think
it needs testing before making into a stable release.
I don't know if you saw this:
On Wed, Nov 17, 2010 at 11:24 AM, Matthias Klose
<email address hidden> wrote:
>> On Sat, Nov 13, 2010 at 10:52 AM, Scott Howard<email address hidden> wrote:
>>> I also don't
>>> know if a user setting LD_LIBRARY_PATH on their own overwrites our
>>> java.library.path
>
> this is incomplete; only works if the jvm is called by the java binary.
>
I'm seeking some more help from java people at sun one last time
before we might have to just say that an incomplete solution might be
the only policy-compliant [1] solution for a non-free package. Please,
if anyone knows of a better way let us know (the joys of non-free
packages: features can be undocumented and a mystery!). The best fix
is to use open-jdk, which I've been suggesting to users.
[1] http:// www.debian. org/doc/ debian- policy/ ch-opersys. html#s9. 9