Novell OPENOFFICE 2.X, Setup Manual, Page: 45 / 53

Customizing an Installation.
Customizing an Installation.
Auto installation
Windows
With OpenOffice.org 1.1.x, Response Files could be used to customize an installation. Now
with 2.x using native installers, this option is no longer available for most operating systems.
Nonetheless, Windows ® installer does offer an alternative for customizing as follows:
1. If you only want to make a silent installation, you can use the /qn parameter from
msiexec.exe (the Windows ® Installer service).
2. If you want to change some other default values in the installation wizard, you can use
the freely available Orca Tool to edit the Windows ® Installer database and to create a
transformation. Then you can start the installation with a command line like:
msiexec.exe /i openoffice.msi /qn TRANSFORMS=myTransform.mst
Of course the creation of the transformation requires some knowledge of the
Windows® Installer database. But for many problems this is not so difficult.
U
NIX ®
based Systems
At the time of preparing this document, all *NIX system installations are, what were called
network installs in 1.1.x, and so there is no specific auto-installation procedure beyond the
default.
Installing individual modules from RPMs
There are occasions where a user will only want to install one or two modules. Doing this is as
easy as a full install from the RPMs; however, doing so requires some knowledge of what to
install. This section addresses this need.
1. Install all core modules as in
rpm -Uhv *core*.rpm
2. Install desired module. For example,
rpm -Uhv openoffice.org-writer-<release>-*.rpm
OpenOffice.org 2.0 Setup Guide 37