Issue 109645

Summary: Make Extenstion Manager GUI optional on install
Product: General Reporter: ohallot <>
Component: uiAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: christoph.lukasiak, cno, issues, joachim.lingner, joerg.skottke, maison.godard, mseidel, oliver.brinzing
Version: OOo 3.2   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: FEATURE Latest Confirmation in: ---
Developer Difficulty: ---

Description ohallot 2010-02-26 16:23:18 UTC

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.

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

Data security policies in these organizations requires that extension should
never be installed by users, and at most, installed under help desk supervision.

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

I recommend to leave the command "unopkg" as it is, since it may be usefull to
install packages without the GUI (for administrative interventions).

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.

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\ 3\URE\bin\regcomp.exe" -revoke -r "C:\Program
Files\ 3\basis\program\services.rdb" -c

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.
Comment 1 Oliver Brinzing 2010-02-27 10:14:01 UTC
Comment 2 Olaf Felka 2010-03-01 06:52:12 UTC