To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=100361
------- Additional comments from mux2...@openoffice.org Fri Mar 20 17:11:00 +0000 2009 ------- Since the bootstrap code distributed with the SDK requires this key, OOo-Dev builds need to write it. Otherwise they cannot be used for tests involving software that interfaces with OOo. If the main purpose of OOo-Dev builds is to show off coming features, that may be fine, but if you want 3rd party developers to use them to test their products with and provide feedback and bug reports, then you need to make sure said 3rd party software won't fail to connect to OOo. If you worry about OOo-Dev builds overwriting this key from a product build, fine, then create the key only if it doesn't already exist. Speaking about OOo-Dev builds, I actually think that the drawbacks of their different behaviour (different registry keys, different directories,...) far outweigh the advantage of being able to install in parallel. I think that most people interested in developer builds would prefer them to behave as product builds since only that allows accurate testing to occur. Sure, casual users curious about upcoming features will prefer something that installs side-by-side to the latest stable version, but since those people rarely file bug reports, are they the important audience to address? If we had the choice we'd use non-OOo-Dev builds for testing, but I'm not aware of a download location for such packages and we don't have build environment for Windows. @is: You mention "WRITE_REGISTRY=1" Is that an environment variable? Will that cause developer builds to create the proper registry keys? --------------------------------------------------------------------- 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: issues-unsubscr...@installation.openoffice.org For additional commands, e-mail: issues-h...@installation.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org