To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=90701
------- Additional comments from [EMAIL PROTECTED] Fri Jun 13 15:23:26 +0000
2008 -------
Crap, its not like I even know what's going on :-)
wrt. a) finding pyuno. We tweak things a bit to make "import uno" work out of
the box anyway by
echo "import sys" > uno.py
echo "sys.path.append('%{basisinstdir}/program')" >> uno.py
and sticking uno.py in the system python place. I believe that ooo-build has a
(nasty hardcoded to /usr/lib) rpath to make "import pyuno" work. So...
cmc->kendy: does running the suse system python with openoffice.org-pyuno
installed and typing into it
import uno
work ?
I'm not sure if that's sufficient, but I assume its necessary anyway.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
