1 ================================================================================ 2 Installation information 3 ================================================================================ 4 5 In order to properly install the bundled extensions, such as dictionaries, it is 6 necessary that the files 7 8 installed 9 ooo_bundled_extensions.xml 10 svc-ooo_bundled_extensions 11 12 are part of the Apache OpenOffice IPS package. They must be added to the package 13 after all other files have been added. Those other files are the SVR4 packages 14 of OOo which can be imported by pkg (pkg import). 15 The files have to be uploaded this way: 16 17 pkgsend -s url_to_pkg_server add file installed mode=644 owner=root group=bin path=${EXTENSIONPATH}/installed restart_fmri=svc:/application/ooo_bundled_extensions:default 18 pkgsend -s url_to_pkg_server add file svc-ooo_bundled_extensions mode=744 owner=root group=bin path=/lib/svc/method/svc-ooo_bundled_extensions 19 pkgsend -s url_to_pkg_server add file ooo_bundled_extensions.xml mode=644 owner=root group=bin path=/var/svc/manifest/application/ooo_bundled_extensions.xml restart_fmri=svc:/system/manifest-import:default 20 21 22 --- 23 24 ${EXTENSIONPATH} must be replaced by the path to the folder containing the 25 bundled extensions. This path changes with every major release of OOo because of 26 the version number which is part of a folder name. The 27 current value is: 28 29 EXTENSIONPATH=/opt/openoffice3/share/extension/install 30 31 The service was tested with OpenSolaris release 2009.6 and may not work with a 32 previous release. 33 34 35 ================================================================================ 36 What do these files do 37 ================================================================================ 38 39 The three files constitute a SMF service. When this service is started, then it 40 installes the bundled extensions which are contained in 41 /opt/openoffice3/share/extension/install. To install them, the service calls 42 "unopkg add --shared ..." with the appropriate arguments. 43 44 The service is started initially after the installation of 45 ooo_bundled_extensions.xml. At this time, all files of OOo, including the 46 extensions, have been copied to their destination. The service calls unopkg on 47 behalf of every extension and adds the path to that extension to the file 48 'installed'. The file 'installed' is used to remember what extensions have 49 already been installed with unopkg. This will prevent to reinstall those 50 extensions whenever the service is restarted. 51 52 When a new version of OOo becomes available, then the respective OOo package 53 contains a new version of 'installed'. That is, it contains a version string, 54 such as 3.2.0. The sole reason for that string is, to change the content of this 55 file in every release. Otherwise IPS would not replace the installed version of 56 'installed' with the one contained in the package. 57 58 The update procedure of OOo will replace 'installed'. 'installed' is associated 59 with a restart_fmri of the service ooo_bundled_extensions. That is after 60 copying 'installed' the service will be restarted. It then installes all 61 extensions contained in /opt/openoffice3/share/extension/install, because 62 the newly installed 'installed' file does not contain any entries yet, except 63 for the version string. 64 65 66 ================================================================================ 67 Known issues 68 ================================================================================ 69 70 If OOo, which contains this service, is uninstalled and later it is installed 71 again, then the bundled extensions are not installed. That is, unopkg is not 72 called to install them with OOo's Extensions Manager. The reasons is a bug in 73 OpenSolaris: 74 75 http://defect.opensolaris.org/bz/show_bug.cgi?id=5742 76 77 To work around this, one can call after uninstalling OOo 78 79 svccfg delete -f ooo_bundled_extensions 80 svccfg delete smf/manifest 81