Type required
Title Changed: Installation of configuration xcu particles
Posted by [EMAIL PROTECTED]
Affected ,officecfg,scp2
Effective from SRC680/cfgimpex


Summary

- $(install)/share/registry/spool/
- gid_Dir_Share_Registry_Spool
+ $(install)/share/registry/modules/org/openoffice/...
+ gid_Dir_Share_Registry_Modules_Oo_...



Description
Installation of configuration xcu particles changed to get rid of the
need to execute configimport --spool during postinstall.

The process to build and deliver these particles in officecfg has been
slightly adjusted. Configuration particle files from other modules can
be built and delivered as before.

SCP items for installation of such particles need to be adjusted as
follows:

- For each configuration component for which installable particles
exist, there needs to be a corresponding directory under
$(install)/share/registry/modules/org/openoffice/... For eample an xcu
particle containing settings for component
org.openoffice.Office.Common needs to be installed into directory
$(install)/share/registry/modules/org/openoffice/Office/Common/, which
is defined in scp2 as gid_Dir_Share_Registry_Modules_Oo_Office_Common

- Configuration particles need to be installed into the directory
corresponding to their component. There is no more automatic
association to the proper component directory from the xcu attributes.

- Configuration particles built in officecfg (using the
install:modules attribute) are now delivered into a different
location. The file entry in scp2 needs to be adjusted accordingly. The
location used here now uses a directory hierachy instead of long
composite names. For example the particle built from
org/openoffice/Office/Common.xcu with install:module="writer" is now
delivered to $(XML)/registry/spool/org/openoffice/Common-writer.xcu.

Changes for all items available in SRC680 m64 have been done.




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to