Difference between revisions of "Documentation/DevGuide/Extensions/unopkg"
| (2 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
|NextPage=Documentation/DevGuide/Extensions/Location of Installed Extensions | |NextPage=Documentation/DevGuide/Extensions/Location of Installed Extensions | ||
}} | }} | ||
| − | + | {{Documentation/DevGuideLanguages|Documentation/DevGuide/Extensions/{{SUBPAGENAME}}}} | |
{{DISPLAYTITLE:unopkg}} | {{DISPLAYTITLE:unopkg}} | ||
The ''unopkg'' executable offers another way to start the Extension Manager. It supersedes the ''pkgchk'' executable which was used in {{PRODUCTNAME}} {{OO1.1.0}} and older versions and which no longer works. | The ''unopkg'' executable offers another way to start the Extension Manager. It supersedes the ''pkgchk'' executable which was used in {{PRODUCTNAME}} {{OO1.1.0}} and older versions and which no longer works. | ||
| Line 21: | Line 21: | ||
The difference is that in the dialog all items deployed under '''{{PRODUCTNAME}} Extensions''' can be modified and new items can be added there as well. All actions, that is, adding, removing, etc. can be done in the dialog. Therefore <tt>unopkg gui</tt> does not require any more parameters. | The difference is that in the dialog all items deployed under '''{{PRODUCTNAME}} Extensions''' can be modified and new items can be added there as well. All actions, that is, adding, removing, etc. can be done in the dialog. Therefore <tt>unopkg gui</tt> does not require any more parameters. | ||
| − | + | Following is a short overview of what can be done with ''unopkg''. Since there are many more commands, have a look at the help text that can be obtained by calling <tt>unopkg -h</tt>. | |
First of all open a console and change into the program directory of the office installation. | First of all open a console and change into the program directory of the office installation. | ||
| Line 45: | Line 45: | ||
When a user starts {{PRODUCTNAME}} and then starts ''unopkg'', then the Extension Manager from the office is used and ''unopkg'' terminates. Then, however, no shared extensions and other shared items can be modified. | When a user starts {{PRODUCTNAME}} and then starts ''unopkg'', then the Extension Manager from the office is used and ''unopkg'' terminates. Then, however, no shared extensions and other shared items can be modified. | ||
| − | {{ | + | {{Warn|Although it is now possible to deploy “live” into a running {{PRODUCTNAME}} process, there are some limitations you should be aware of: Removing a type library from a running process is not possible, because this may lead to crashes when the type is needed. Thus if you, for example, uninstall a package that comes with a UNO type library, these types will vanish upon next process startup, but not before. |
There may also be problems with cached configuration data, because parts of the running process do not listen for configuration updates (for example, menu bars). Most often, those parts read the configuration just once upon startup.}} | There may also be problems with cached configuration data, because parts of the running process do not listen for configuration updates (for example, menu bars). Most often, those parts read the configuration just once upon startup.}} | ||
Revision as of 07:32, 12 July 2018
The unopkg executable offers another way to start the Extension Manager. It supersedes the pkgchk executable which was used in OpenOffice.org 1.1.0 and older versions and which no longer works.
In contrast to the Extension Manager in OpenOffice.org unopkg can also manage shared extensions. For example:
[<OfficePath>/program] $ unopkg add --shared my_extension.oxt
installs my_extension.oxt for all users.
unopkg offers a windowless mode in which all interactions occurs through the console. This is the default. If unopkg is started with the subcommand gui then the Extension Manager dialog appears which is exactly the same as the one in OpenOffice.org.
[<OfficePath>/program] $ unopkg gui
The difference is that in the dialog all items deployed under OpenOffice.org Extensions can be modified and new items can be added there as well. All actions, that is, adding, removing, etc. can be done in the dialog. Therefore unopkg gui does not require any more parameters.
Following is a short overview of what can be done with unopkg. Since there are many more commands, have a look at the help text that can be obtained by calling unopkg -h.
First of all open a console and change into the program directory of the office installation.
Adding an extension for a single user:
[<OfficePath>/program] $ unopkg add my_extension.oxt
Adding an extension for all users:
[<OfficePath>/program] $ unopkg add --shared my_extension.oxt
Removing a user extension is done via the identifier of the extension (see Extension Identifiers):
[<OfficePath>/program] $ unopkg remove my.domain.my_extension-id
Remove a shared extension:
[<OfficePath>/program] $ unopkg remove --shared my.domain.my_extension-id
Before you install an extension or other item for all users, make absolutely sure there are no running instances of OpenOffice.org. unopkg cannot recognize if there are running instances of OpenOffice.org from different users. Installing into a running office installation might cause inconsistencies and destroy your installation!
When a user starts OpenOffice.org and then starts unopkg, then the Extension Manager from the office is used and unopkg terminates. Then, however, no shared extensions and other shared items can be modified.
 |
Although it is now possible to deploy “live” into a running OpenOffice.org process, there are some limitations you should be aware of: Removing a type library from a running process is not possible, because this may lead to crashes when the type is needed. Thus if you, for example, uninstall a package that comes with a UNO type library, these types will vanish upon next process startup, but not before.
There may also be problems with cached configuration data, because parts of the running process do not listen for configuration updates (for example, menu bars). Most often, those parts read the configuration just once upon startup. |
| Content on this page is licensed under the Public Documentation License (PDL). |
