To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69940
User is changed the following:
What |Old value |New value
================================================================================
Status|NEW |RESOLVED
--------------------------------------------------------------------------------
Resolution| |FIXED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Mon Oct 9 02:35:20 -0700
2006 -------
I prepared the following solution:
All extensions that need to be registered have to be installed into the
directory
/share/extension/install
Windows: This is the easiest solution. There are two new CustomActions executed
at the end of the installation and at the start of the deinstallation. This
CustomAction at the end of the installation registers all extensions, that are
located in share/extension/install.
Solaris: There are new scripts, that will be installed into the program
directory. This scripts have the names "register_extensions" and
"deregister_extensions". This scripts register or deregister all extension that
can be found in share/extension/install. After the installation of all packages,
the script "register_extensions" has to be executed by hand. That has to be
mentioned in the readme files.
Linux: Every extension has to be included into a rpm. The rpms with extensions
have several scripts included, in which unopkg is called. This is required in
"preinstall", "postinstall" and "preremove". Therefore the extension is
registered after the rpm installation and deregistered if the rpm is removed.
Additionally the scripts "register_extensions" and "deregister_extensions" (see
the Solaris section) are also available in the program directory.
Programming requirements:
For integrating an extension into an installation set, it it necessary to define
the new oxt file in project scp2 (no special flag required). It is important,
that the destination directory is gid_Dir_Share_Extension_Install.
Because every extension has to have its own rpm or Solaris package, it is also
necessary, to define a new module in scp2. This allows also the
selection/deselection of the extension during Custom setup.
In instsetoo_native it is requrired, that the Unix package for this module is
defined. This happens in instsetoo_native/inc_openoffice/unix/packagelist.txt.
The new package has a dependency to the package core02, which contains the
unopkg executable. Additionally this new packages must include as script the
script file "shellscripts_extensions.txt", that contains the three scripts for
RPM installation.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
