To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=97629
User sb changed the following:
What |Old value |New value
================================================================================
CC|'aziem' |'aziem,jbu'
--------------------------------------------------------------------------------
Ever confirmed| |1
--------------------------------------------------------------------------------
Status|UNCONFIRMED |STARTED
--------------------------------------------------------------------------------
Target milestone|--- |OOo 3.1
--------------------------------------------------------------------------------
------- Additional comments from s...@openoffice.org Wed Jan 7 16:56:49 +0000
2009 -------
@jbu: officehelper.py (per default left in the basis layer program directory
after the three layer split) expectes to find the soffice executable next to
itself (which no longer works, as the soffice executable moved to the brand
layer).
When the OOo-specific python executable (from the brand layer program directory)
is used, it already modifies PYTHONPATH so that files like officehelper.py are
found in the first place (and code like "from officehelper import bootstrap"
works at all). Something similar could be used to communicate from the
OOo-specific python executable (which can know where soffice is located) to
officehelper.py (which cannot know by itself, if it remains in the basis layer)
where soffice is located. (For example, using the UNO_PATH environment variable
that is already used, somewhat related, in cppuhelper_detail_findSofficePath.)
However, when a system-provided python executable is used instead (i.e., OOo is
configured to not provide an own python executable), I am unsure how such a
mechanism could work, but I am also unsure whether code like "from officehelper
import bootstrap" would work there in the first place, as PYTHONPATH would
probably not be set accordingly (we already discussed that before, but I cannot
remember that this general problem was solved).
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@udk.openoffice.org
For additional commands, e-mail: issues-h...@udk.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
