To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=41034
------- Additional comments from [EMAIL PROTECTED] Wed Feb 2 10:45:48 -0800 2005 ------- Hi Michael, Jan, Regarding your question about what's going on (and how this relates to the micro-deployment doc)... The change to remove usage of osl_getExecutableFile() (and replace it by the technique illustrated in the micro-deployment doc, which is the technique used to find deployment-time (subsystem) configuration like boostraprc and configmgrrc) was induced by issue 35209 (soffice crashes under valgrind 2.2 due to not finding it's resource files beneath an executable file '/usr/local/bin/valgrind'). Thus, the ResMgr (subsystem) should not make assumptions about the executable file, but rely on it's deployment-time configuration of where the resource files are installed. So, the new design assumes 'ResMgr' and '<instpath>/program/resource' do form a 'sub-system' within an office installation, the latter (path) being an implementation artifact of the former (ResMgr). Sorry for the lengthy explanation, but I hope it clarifies matters, and you've asked for it :-) To conclude, yes, I guess you should indeed use the STAR_RESOURCEPATH environment variable as a fallback. Hope that helps, Matthias --------------------------------------------------------------------- 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]
