Hi,
python is the public interface, python.sh is an implemetation detail.
I actually introduced this because I didn't know how to create a python
script with our installation procedure when there is the python as
executable in the solver path in the build environment. (In the build
env, it is ok to just call python executable as the appropriate
environment gets set by the global build env scropt).
It is not needed at all for SYSTEM_PYTHON, because python is then
installed elsewhere anyway (e.g. /usr/local/bin/python).
ok ?
Bye,
Joerg
Stephan Bergmann wrote:
Why are there both a pyhton.sh and a python symlink to it in the program
directory of OOo 2.x (when defined UNX && !defined SYSTEM_PYTHON)? Are
both part of the OOo public interface (intended to be called by
clients), or should one or the other be considered an implementation
detail?
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
