To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=86525
------- Additional comments from [EMAIL PROTECTED] Thu Feb 28 14:18:44 +0000 2008 ------- > fst > From a quick look into the deliver-patch - if I understand it right, you > changed it to always re-register UNO components which have been changed Not quite - I changed it to register UNO components as they are installed into the solver [ at least into an RDB file for that module ]; this was never the case in the past, registration occuring only as an install-set is produced. > Which sounds questionable and unnecessarily expensive, IMO. > Personally, I'd prefer this being an explicit thing, to be done > when I actually embark upon running a unit test. But that might be only me. Clearly scanning all .so files to build a complete .rdb file each time a unit test is called (ie. per module) adds some N^2 load / relocate / test issue, whereas merging the .rdb files adds only an N^2 in merging simple. rdb files, a rather fast operation in comparison. My request for a decision on merging cpputools/source/registercomponent into cppuhelper, or re-arranging dependencies there is key here though. --------------------------------------------------------------------- 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]
