To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109645 Issue #|109645 Summary|Make Extenstion Manager GUI optional on install Component|framework Version|OOo 3.2 Platform|All URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|FEATURE Priority|P3 Subcomponent|ui Assigned to|tm Reported by|ohallot
------- Additional comments from ohal...@openoffice.org Fri Feb 26 16:23:18 +0000 2010 ------- Objective Make the Extension Manager GUI as an option on installation, by splitting it from core package and puting it into an optional package, installable by default. Motivation: In many large corporations and in public administration, tight data security policies are enforced for the users. Among one of potential threats are the unauthorized installation of softwares. That includes extensions for OpenOffice.org Data security policies in these organizations requires that extension should never be installed by users, and at most, installed under help desk supervision. Solution: Separate the Extension Manager GUI from core package and place it as an optional feature on installation, so it can be removed/controlled from default installation. On Windows environments, the "msiexec" command should have a extra component (see how it was done for the OO Improvement program). on Linux and others, a separated rpm/dmg package Note: I recommend to leave the command "unopkg" as it is, since it may be usefull to install packages without the GUI (for administrative interventions). Note2: You may ask why leave unopkg in the package and remove the GUI, since the user will still be able to install extensions. Well, the purpose is to make the life of the average user harder. Admitedly, we cannot prevent a skilled user to use unopkg in the command line. Note3: The usual command to remove the Extension manager GUI is to revoke a dll. Up to OO 3.1, the command was C:\Program Files\OpenOffice.org 3\URE\bin\regcomp.exe" -revoke -r "C:\Program Files\OpenOffice.org 3\basis\program\services.rdb" -c "vnd.sun.star.expand:$OOO_BASE_DIR/program/deploymentguimi.uno.dll" But in OO 3.2 $OOO_BASE_DIR changed to $BRAND_BASE_DIR So it makes a matter of moving target on each release of OO with respect to revoking the Extension Manager GUI. This hurts automated installations. --------------------------------------------------------------------- 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...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
