One design that comes to mind is how distro populate their default
environment. Instead of shoving everything in a single file there is a
top file that source the content of a directory. Depending on your
distro it could be in /etc/env.d or /etc/profile.d.
So individual package can put particular s
Yes, but in the absence of an achieved utopia, is there something we can do
here? I see that sage-env already has a lot of LD_LIBRARY_PATH hacking in
it. Might be good to design a system for regularizing this, and moving all
this hacking to that system.
My solution has been to add Python code
On 2015-09-21 19:23, Bill Janssen wrote:
On OS X, The CasADi subsystem now installs its dynamic
libraries in a subdirectory of JModelica, a subdirectory which then has
to be put on the LD_LIBRARY_PATH the Python interpreter is run with
That is clearly an issue with the build system. Instead of re
I'm updating an old-style JModelica spkg to version 1.16, which just came
out. On OS X, The CasADi subsystem now installs its dynamic libraries in a
subdirectory of JModelica, a subdirectory which then has to be put on the
LD_LIBRARY_PATH the Python interpreter is run with, as CasADi is package
