Issue 79648 - do not use lock file when installing bundled extensions
Summary: do not use lock file when installing bundled extensions
Status: CLOSED DUPLICATE of issue 77196
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 680m220
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: joachim.lingner
QA Contact: issues@framework
URL:
Keywords:
: 80564 86080 (view as issue list)
Depends on:
Blocks: 79790
  Show dependency tree / graph
 
Reported: 2007-07-16 09:36 UTC by joachim.lingner
Modified: 2013-08-07 15:31 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description joachim.lingner 2007-07-16 09:36:14 UTC 
... because if the user uses sudo  this may create the user installation
directory and the lock file with root access. The user will not be able to
modify it later on.
Comment 1 joachim.lingner 2007-07-16 09:38:29 UTC 
see also tr 148665
Comment 2 joachim.lingner 2007-07-19 12:45:11 UTC 
The fix for i79643 also fixes this problem. However, we should prevent writing
the lock file altogether. Therefore I will keep this open.
Comment 3 joachim.lingner 2007-08-10 09:50:36 UTC 
*** Issue 80564 has been marked as a duplicate of this issue. ***
Comment 4 joachim.lingner 2007-10-18 14:29:37 UTC 
Retargeted to 3.0.
Comment 5 joachim.lingner 2008-03-17 10:47:06 UTC 
*** Issue 86080 has been marked as a duplicate of this issue. ***
Comment 6 joachim.lingner 2008-03-17 10:50:28 UTC 
We may use a new command line switch -nolockfile which is only valid together
with --shared (because then no other user should be using the office).
Comment 7 ccheney 2008-04-23 12:27:42 UTC 
Please make sure this is done for OOo 3.0, it is causing major problems with
package installation since unopkg is used in deb/rpm's to register extensions.
We are having to drop the writer2latex extension on Ubuntu 8.04 because unopkg
won't work reliably and is causing install failures.
Comment 8 joachim.lingner 2008-04-25 06:58:40 UTC 
As obr indicated in issue 86080 we may just implement an option for the script
which does not affect the behaviour of --shared.
We need to think about Windows. Although it does not come with sudo, I am sure
there are implementation around which try to emulate it. If so, we'd have a
problem since there is no unopkg script on Windows ....
Comment 9 joachim.lingner 2008-04-25 07:32:57 UTC 
A work around is to start unopkg with additional bootstrap parameters. For example

unopkg -env:UserInstallation=file:////var/temp/myuserinstallation
-env:UNO_JAVA_JFW_INSTALL_DATA=$$ORIGIN/../share/config/javasettingsunopkginstall.xml
      ....

The first -env causes that the whole user installation is redirected. The script
which invokes unopkg needs to make sure that the directory exists and delete it
later on. The second -env is to provide a location for the java settings. If you
 run unopkg several times then use the same value (do not delete it). It causes
that the first unopkg searches for a suitable JRE, writes the settings to that
file. All other unopkg calls later on will reuse these settings. However, after
changing the directory structure of OOo, the URL is probably wrong.
Comment 10 joachim.lingner 2008-05-30 15:20:27 UTC 
.
Comment 11 joachim.lingner 2010-06-11 10:11:10 UTC 
unopkg is not used anymore during setup, so the issue is invalid

*** This issue has been marked as a duplicate of 77196 ***
Comment 12 joachim.lingner 2010-06-11 10:11:36 UTC 
.