Difference between revisions of "Documentation/Administration Guide/Using Package Manager"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (To Remove an Extension for All Users)
 
(46 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:Using the {{OOo}} Extension Manager}}
 
 
{{Documentation/AdminGuideTOC/v2
 
{{Documentation/AdminGuideTOC/v2
 
|ShowPrevNext=block
 
|ShowPrevNext=block
Line 6: Line 5:
 
|NextPage=Documentation/Administration_Guide/Adding_Template_Files
 
|NextPage=Documentation/Administration_Guide/Adding_Template_Files
 
|PrevPage=Documentation/Administration_Guide/Using_Custom_Macros_and_Libraries
 
|PrevPage=Documentation/Administration_Guide/Using_Custom_Macros_and_Libraries
}}
+
}}  
 
+
{{DISPLAYTITLE:{{AOo}} Extension Manager}}
You can use the {{OOo}} Extension Manager to add, remove, disable, enable, and export {{OOo}} extensions. For example, you can use the Extension Manager to add or remove the following types of extensions:
+
__NOTOC__
 +
You can use the {{AOo}} Extension Manager to add, remove, disable, enable, or export {{AOo}} extensions. For example, you can use the Extension Manager to add or remove the following types of extensions:
 
* Configuration Data
 
* Configuration Data
 
* Configuration Libraries
 
* Configuration Libraries
 
* Extensions
 
* Extensions
* Universal Network Objects (UNO) components<br>These components represent compiled software packages. UNO is the interface-based component model for {{OOo}}. For more information on this model, go to the [http://udk.openoffice.org UNO Development Kit project web site].
+
* Universal Network Objects (UNO) components<br>These components represent compiled software packages. UNO is the interface-based component model for {{AOo}}. For more information on this model, go to the [https://www.openoffice.org/udk/ UNO Development Kit project website].
  
{{Documentation/Note|You cannot manage XSLT filters, language modules, or palettes with the Extension Manager.}}
+
{{Note|You cannot manage XSLT filters, language modules, or palettes with the Extension Manager.}}
  
You can manage extensions from a dialog box or a command-line.
+
You can manage extensions from a dialog box or from the command-line.
  
==Using the Extension Manager Dialog Box==
+
Extensions can be installed, so they are available to either the current user (single user installation), or to all users (shared user installation).
  
You can open the Extension Manager dialog box from the '''Tools''' menu in any {{OOo}} Program. However, to add packages for all users of a {{OOo}} installation, you need to open the Extension Manager dialog box from the command-line.
+
== Single user install ==
 +
To install an extension for the current user, open the Extension Manager dialog box from the {{menu|Tools}} menu in any {{AOo}} program and install the extension. The extension will be installed and be immediately available to the current user. The extension will not be available to other users on this computer.
  
===To Add a Package With the Extension Manager Dialog Box===
+
== Shared user install ==
 +
To install an extension for all users (shared user installation), you must install the extension as root or Administrator.  You can do this from the command line (recommended), or from the {{AOo}} Extension manager.
  
# Become root.
+
=== Using the Extension manager===
#* In UNIX and Linux, open a terminal, and type <tt>su</tt>
+
To install an extension for all users on a single machine, you can use the {{AOo}} Extension manager. You must be running {{AOo}} as root or Administrator.
#* In Windows, open a Command Prompt.
+
# Change to the <tt>&lt;{{OOo}} installation directory&gt;/{{OOo}}2/program</tt> directory.
+
# Type <tt>unopkg gui</tt><br>The Extension Manager dialog box opens.
+
# In the list of extensions, select the extension category that you want to add the extension to.
+
# Click the '''Add''' button.
+
# Locate the extension that you want to add, and then click the '''Open''' button.
+
  
===To Remove an Extension With the Extension Manager Dialog Box===
+
Open the Extension Manager dialog box from the {{menu|Tools}} menu in any {{AOo}} program and install the extension. You will be asked "For whom do you want to install the extension?". Select {{button|For all users}} and complete the installation. The extension will be installed and be immediately available to all users.
 +
 
 +
===Using the command line===
 +
To install an extension for all users, you can use the <tt>unopkg add --shared</tt> command-line application. You must have root or Administrator privileges.
 +
 
 +
==== To Add an Extension for All Users ====
  
 
# Become root.
 
# Become root.
#* In UNIX and Linux, open a terminal, and type <tt>su</tt>
+
#* In UNIX, Linux and OSX, open a terminal window, type <tt>su</tt> and enter your root user password.
#* In Windows, open a Command Prompt.
+
#* In Windows 7, 10, right-click the icon for the Command Prompt and select Run as Administrator.
# Change to the <tt> &lt;{{OOo}} installation directory&gt;/{{OOo}}2/program</tt> directory.
+
# Change to the <tt>''install-dir''/program</tt> directory.
# Type <tt>unopkg gui</tt><br>The Extension Manager dialog box opens.
+
# Type <tt>unopkg add --shared ''package-name''</tt>.
# In the list of extensions, select the extension that you want to remove.
+
# Click the '''Remove''' button.
+
  
==Using the <tt>unopkg</tt> Command to Manage Extensions==
+
====To Remove an Extension for All Users ====
  
You can manage packages from the command line. The syntax for the <tt>unopkg</tt> command is as follows:
+
# Become root.
 +
#* In UNIX, Linux,and OSX, open a terminal window, and type <tt>su</tt>.
 +
#* In Windows Vista and Windows 7, 10, right-click on the icon for the Command Prompt and select Run as Administrator.
 +
# Change to the <tt>''install-dir''/program</tt> directory.
 +
# Type <tt>unopkg remove ''package-name''</tt>.
  
unopkg add {v, f, log-file, shared} extension-path | remove {v, f, log-file, shared} extension-name | list {v, f, log-file, shared} extension-name | reinstall {v, f, log-file, shared} | gui | -V | -h
+
==Using the <tt>unopkg</tt> Command to Manage Extensions==
  
;<tt>add</tt>:Adds extensions to a {{OOo}} installation.
+
You can manage packages from the command line. The syntax for the <tt>unopkg</tt> command is:
;<tt>remove</tt>:Removes extensions from a {{OOo}} installation.
+
<syntaxhighlight lang="text">
 +
unopkg add {-v, -f, --log-file, --shared} extension-path
 +
        remove {-v, -f, --log-file, --shared} extension-name
 +
        list {-v, -f, --log-file, --shared} extension-name
 +
        reinstall {-v, -f, --log-file, --shared}
 +
        gui
 +
        -V
 +
        -h
 +
</syntaxhighlight>
 +
;<tt>add</tt>:Adds extensions to an {{AOo}} installation.
 +
;<tt>remove</tt>:Removes extensions from an {{AOo}} installation.
 
;<tt>list</tt>:Displays information about the deployed extensions.
 
;<tt>list</tt>:Displays information about the deployed extensions.
;<tt>reinstall</tt>:Reinstalls the deployed extensions.
+
;<tt>reinstall</tt>:Re installs the deployed extensions.
 
;<tt>gui</tt>:Opens the Extension Manager dialog box.
 
;<tt>gui</tt>:Opens the Extension Manager dialog box.
 
;<tt>–V, – –version</tt>:Displays the version information for the <tt>unopkg</tt> command.
 
;<tt>–V, – –version</tt>:Displays the version information for the <tt>unopkg</tt> command.
Line 58: Line 71:
 
;<tt>-v, --verbose</tt>:Runs the command in verbose mode.
 
;<tt>-v, --verbose</tt>:Runs the command in verbose mode.
 
;<tt>-f, --force</tt>:Overwrites existing extensions that have the same names.
 
;<tt>-f, --force</tt>:Overwrites existing extensions that have the same names.
;<tt>--log-file &lt;filename&gt;</tt>:Creates a log file. The default file name path for the log file is <tt>&lt;cache-dir&gt;/log.txt</tt>
+
;<tt>--log-file ''filename''</tt>:Creates a logfile. The default filename path for the logfile is <tt>''cache-dir''/log.txt</tt>
 
;<tt>--shared</tt>:Expert feature: operate on shared installation deployment context; run only when no concurrent processes are running
 
;<tt>--shared</tt>:Expert feature: operate on shared installation deployment context; run only when no concurrent processes are running
  
 +
{{InterWiki Languages AdminGuide|articletitle=Documentation/Administration Guide/Using Package Manager}}
 
{{PDL1}}
 
{{PDL1}}

Latest revision as of 09:57, 1 May 2022


You can use the Apache OpenOffice Extension Manager to add, remove, disable, enable, or export Apache OpenOffice extensions. For example, you can use the Extension Manager to add or remove the following types of extensions:

  • Configuration Data
  • Configuration Libraries
  • Extensions
  • Universal Network Objects (UNO) components
    These components represent compiled software packages. UNO is the interface-based component model for Apache OpenOffice. For more information on this model, go to the UNO Development Kit project website.
Documentation note.png You cannot manage XSLT filters, language modules, or palettes with the Extension Manager.

You can manage extensions from a dialog box or from the command-line.

Extensions can be installed, so they are available to either the current user (single user installation), or to all users (shared user installation).

Single user install

To install an extension for the current user, open the Extension Manager dialog box from the Tools menu in any Apache OpenOffice program and install the extension. The extension will be installed and be immediately available to the current user. The extension will not be available to other users on this computer.

Shared user install

To install an extension for all users (shared user installation), you must install the extension as root or Administrator. You can do this from the command line (recommended), or from the Apache OpenOffice Extension manager.

Using the Extension manager

To install an extension for all users on a single machine, you can use the Apache OpenOffice Extension manager. You must be running Apache OpenOffice as root or Administrator.

Open the Extension Manager dialog box from the Tools menu in any Apache OpenOffice program and install the extension. You will be asked "For whom do you want to install the extension?". Select  For all users  and complete the installation. The extension will be installed and be immediately available to all users.

Using the command line

To install an extension for all users, you can use the unopkg add --shared command-line application. You must have root or Administrator privileges.

To Add an Extension for All Users

  1. Become root.
    • In UNIX, Linux and OSX, open a terminal window, type su and enter your root user password.
    • In Windows 7, 10, right-click the icon for the Command Prompt and select Run as Administrator.
  2. Change to the install-dir/program directory.
  3. Type unopkg add --shared package-name.

To Remove an Extension for All Users

  1. Become root.
    • In UNIX, Linux,and OSX, open a terminal window, and type su.
    • In Windows Vista and Windows 7, 10, right-click on the icon for the Command Prompt and select Run as Administrator.
  2. Change to the install-dir/program directory.
  3. Type unopkg remove package-name.

Using the unopkg Command to Manage Extensions

You can manage packages from the command line. The syntax for the unopkg command is:

 unopkg add {-v, -f, --log-file, --shared} extension-path
        remove {-v, -f, --log-file, --shared} extension-name
        list {-v, -f, --log-file, --shared} extension-name
        reinstall {-v, -f, --log-file, --shared}
        gui
        -V
        -h
add
Adds extensions to an Apache OpenOffice installation.
remove
Removes extensions from an Apache OpenOffice installation.
list
Displays information about the deployed extensions.
reinstall
Re installs the deployed extensions.
gui
Opens the Extension Manager dialog box.
–V, – –version
Displays the version information for the unopkg command.
–h, – –help
Displays the help for the unopkg command.
-v, --verbose
Runs the command in verbose mode.
-f, --force
Overwrites existing extensions that have the same names.
--log-file filename
Creates a logfile. The default filename path for the logfile is cache-dir/log.txt
--shared
Expert feature: operate on shared installation deployment context; run only when no concurrent processes are running
Content on this page is licensed under the Public Documentation License (PDL).
Personal tools
In other languages