OpenOffice.org Extension Manager
- Custom OpenOffice.org Basic Macros and Libraries
- [[EN/documentation/administration_guide/using_package_manager|]]
- Adding Template Files to an OpenOffice.org Installation
- Adding AutoText Files to an OpenOffice.org Network Installation
- Deactivating the OpenOffice.org Registration Wizard
- Accessing Email Clients
- Customizing the User Interface
- Restricting Functionality in OpenOffice.org
- Accessing OpenOffice.org User Profiles on an LDAP Server
You can use the OpenOffice.org Extension Manager to add, remove, disable, enable, or export OpenOffice.org 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 OpenOffice.org. For more information on this model, go to the UNO Development Kit project web site.
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 OpenOffice.org 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 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 OpenOffice.org Extension manager.
Using the Extension manager
To install an extension for all users on a single machine, you can use the OpenOffice.org Extension manager. You must be running OpenOffice.org as root or Administrator.
Open the Extension Manager dialog box from the Tools menu in any OpenOffice.org 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 install. 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
- Become root.
- In UNIX, Linux and OSX, open a terminal window, type su and enter your root user password.
- In Windows XP, open a command prompt.
- In Windows Vista and Windows 7, right-click the icon for the Command Prompt and select Run as Administrator.
- Change to the install-dir/program directory.
- Type unopkg add --shared package-name.
To Remove an Extension for All Users
- Become root.
- In UNIX, Linux,and OSX, open a terminal window, and type su.
- In Windows XP, open a command prompt.
- In Windows Vista and Windows 7, right-click on the icon for the Command Prompt and select Run as Administrator.
- Change to the install-dir/program directory.
- 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 OpenOffice.org installation.
- remove
- Removes extensions from an OpenOffice.org installation.
- list
- Displays information about the deployed extensions.
- reinstall
- Reinstalls 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 log file. The default file name path for the log file 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). |