david.dehaven at oracle.com
Mon Feb 24 15:15:34 PST 2014
> Application. Signed, not sandboxed. Something recently, Lion -> Mountain Lion maybe? seemed not to work unless I signed it. So I self-signed. I first looked at this a while ago I think before it was even signed and still couldn't get it to work.
I don't know what the core issue is but my own (personal) experience has been that LSEnvironment isn't reliable.
> I'm trying to interface 3rd party code to my HalfPipe application. It's a JSR 223 interface to the R language.
> It seems to require a R_HOME environment variable set. Which so far, I can't give it with LSEnvironment through the plist.
Requiring R_HOME to be set in the environment seems sketchy to me. At worst you should be able to set it through a system property, not rely on the environment. Is it open source? Maybe it could be fixed and contributed back.
The ugly workaround might be to drill down through JNI to call setenv, if it can be done early enough.
More information about the macosx-port-dev