Return-Path: 
 <ooo-issues-return-11331-apmail-incubator-ooo-issues-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-ooo-issues-archive@minotaur.apache.org
Delivered-To: apmail-incubator-ooo-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id EB6B8C217
	for <apmail-incubator-ooo-issues-archive@minotaur.apache.org>;
 Wed, 13 Jun 2012 16:14:06 +0000 (UTC)
Received: (qmail 79168 invoked by uid 500); 13 Jun 2012 16:14:06 -0000
Delivered-To: apmail-incubator-ooo-issues-archive@incubator.apache.org
Received: (qmail 79148 invoked by uid 500); 13 Jun 2012 16:14:06 -0000
Mailing-List: contact ooo-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ooo-issues-help@incubator.apache.org>
List-Unsubscribe: <mailto:ooo-issues-unsubscribe@incubator.apache.org>
List-Post: <mailto:ooo-issues@incubator.apache.org>
List-Id: <ooo-issues.incubator.apache.org>
Reply-To: ooo-issues@incubator.apache.org
Delivered-To: mailing list ooo-issues@incubator.apache.org
Received: (qmail 79139 invoked by uid 99); 13 Jun 2012 16:14:06 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2012 16:14:06 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.123] (HELO sif.zones.apache.org) (140.211.11.123)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2012 16:14:05 +0000
Received: by sif.zones.apache.org (Postfix, from userid 80)
	id 6A0F76A47; Wed, 13 Jun 2012 16:13:45 +0000 (UTC)
From: bugzilla@apache.org
To: ooo-issues@incubator.apache.org
Subject: [Bug 119272] user directory file size grows to 160mb due to bundled
 extensions
Date: Wed, 13 Jun 2012 16:13:43 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: installation
X-Bugzilla-Component: code
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: major
X-Bugzilla-Who: af@a-w-f.de
X-Bugzilla-Status: CONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ooo-issues@incubator.apache.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-119272-248469-ZRkWiQFtOS@https.issues.apache.org/ooo/>
In-Reply-To: <bug-119272-248469@https.issues.apache.org/ooo/>
References: <bug-119272-248469@https.issues.apache.org/ooo/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://issues.apache.org/ooo/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Virus-Checked: Checked by ClamAV on apache.org

https://issues.apache.org/ooo/show_bug.cgi?id=119272

--- Comment #11 from Andre <af@a-w-f.de> ---
One technical part of installing extensions system wide is the following code
snippet.  It starts unopkg.exe with elevated access rights:

HINSTANCE nResult (ShellExecute(
    NULL,
    "runas",
    "<office-path>\\program\\unopkg.exe",
    "gui",
    "<office-path>\\program",
    SW_SHOW));

For operating systems other than Windows we will need other solutions.

But the main problem is how to convince the user/admin to type in her password.
 Just to recap, here is how the installation process could work with shared
extensions:

1. Admin installs office (a user without admin rights can not elevate his
access rights high enough to install anything).  During the installation she is
asked for her password to allow the installer to write into system directories
(c:\Program Files or /usr/bin etc).  It is operating system dependent of who
does the asking, on Windows it is our installer, on Linux the package
installer.

2. Office is started for the first time.  Only at this stage we can install
extensions (no installer on Mac, legal restrictions).  In order to install them
shared for all users we need elevated access rights a second time. 
Inconvenient but better then user install because of $TITLE.

3. Now the new part.  Initiate the shared installation somewhere in the desktop
module, where the user installation is started today.  Show a dialog that tells
the user that we are about to ask for his password, again, in order to install
the extensions, and save his disk space.  On his OK make a call like the one
above which will result in the desktop code executed in another process with
elevated rights.  Install the extensions.

4. Everybody is happy.

-- 
You are receiving this mail because:
You are the assignee for the bug.