To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=60696
------- Additional comments from [EMAIL PROTECTED] Mon Jun 11 14:29:43 +0000 2007 ------- @kendy: For just one platform with just one use case 1 manday of testing may be right. But OOo is not just designed for one use case on one single platform. I've already seen the last patch from Aug, 22th, but MBA already stated what's missing. The pipe name will only be the same if you don't touch the bootstraprc and don't make use of -env switch. The patch just works for the "default" use case - not more. 1. Link against SAL and use rtl/bootstrap functions to support full bootstrap variable support 2. Support -env command line Linking against SAL is not what I would prefer - I already stated what kind of aproach would be better. But if you want it to get into the master quickly without finding dedicated solutions for each use case we must ensure that there will be no regressions. If you agree with this quick approach please come along with an adjusted patch. Regarding the "silver plate" - you know - you got 10 million lines of working code on a silver plate too ;-) The problem is that developing a prototype that works with 90 percent of the use cases takes 10 percent of development time. The other 90 percent of time are used to fix the missing 10 percent and make it reliable, maintainable. Regardless whether this relation is 90/10 or 70/30 - this is common software development knowledge. Writing a prototype is always fast, easy and very satisfying ;-) Second quick approach: As I understand the patch ooqstart is the loader used for system integration and for starting OOo within your distribution. The existing soffice.bin code is mostly untouched with just minor changes when updating the splash screen and instantiating a splashscreen service. So with your distribution if you start soffice.bin with a modified bootstraprc (UserInstallationPath != SYSUSERCONFIG) and start ooqstart afterwards you will get a second instance and will not find the running soffice.bin process. So would it be O.K. to leave the patch as it is but don't use ooqstart in the official OOo build or advertise it as a goody with the hint "this only works if you don't touch the bootstraprc and user configuration resolving will be disabled/not working" ? --------------------------------------------------------------------- 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]
