To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=105059 Issue #|105059 Summary|No longer set PYTHONPATH in build environment Component|tools Version|current Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|ENHANCEMENT Priority|P3 Subcomponent|configure Assigned to|sb Reported by|sb
------- Additional comments from [email protected] Mon Sep 14 13:04:46 +0000 2009 ------- Issue 101213 took care to set the PYTHONPATH environment variable consistently in all build environments (configure as well as setsolar based ones). It was recently noticed (Sun-Hamburg internal thread "Re: Mercurial-Implementation: hg clients available for all supported platforms" on sun.star.eng.discuss, starting Sep 1, 2009) that when the fix for that issue 101213 will be integrated into the master, at least Sun-Hamburg developers will have a hard time executing hg from within the (setsolar) build environment. Now, issue 101213, included in <http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fsb113>, is scheduled for integration in one of the next DEV300 milestones, probably DEV300m59. To prevent the hg problems outlined above, I ask kz (who does the integration for DEV300m59) to masterfix DEV300m59 after integration of CWS sb113, namely to remove all the occurrences of setting PYTHONPATH from solenv/config/sdev300.ini. This should have no negative impact, as it will effectively merely restore the state before the fix for issue 101213 (which did not fix any build breakers or things like that, instead just addressed a little unfortunate inconsistency). For convenience, I will attach an appropriate patch for that masterfix to this issue. With that settled, I would like to address the original issue of inconsistent PYTHONPATH settings in the (obviously) right way, by removing setting that environment variable from all build environments. It appears that most (if not all) of the places that require PYTHONPATH being set during the build already take care to set it explicitly, anyway (in DEV300m58, see makefile.rc, instsetoo_native/util/makefile.mk, python/Python-2.6.1-mingw.patch, pyuno/demo/pyunoenv.bat, pyuno/demo/pyunoenv.tcsh, smoketestoo_native/smoketest.pl). Additional processes like the test described at <http://wiki.services.openoffice.org/w/index.php?title=Uno/Binary/Modules/testtools&oldid=39651#Tests> will have to be adapted to explicitly set PYTHONPATH. (In DEV300m58, there is an odd little script solenv/bin/pchdelta that explicitly unsets PYTHONPATH before calling python; maybe that is not needed any longer after fixing this issue.) --------------------------------------------------------------------- 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]
