CWS Networker3

OpenOffice.org 2.0 / StarOffice 8

Document - ID	Specification Owner	Last Change	Status
	Ingo Schmidt	28.05.04	Final
Conforms to	
Applies to	Installation
Task ID(s)	i25326
Category	Feature

Abstract

The CWS “networker3” has to be created to “synchronize” the old setup application with the new installation mechanism using native installers. The old setup application supported Star­Office/OpenOffice.org specific installation mechanisms, that are not supported by native installers or differently supported by native installers. There are especially two items in the installation set description language scp that can be converted into the native installer packaging mechanism only with difficulties: CustomActions and Procedures. Both describe the possibility of direct code execution during the installation process using the old setup application. The native installer offer different ways for direct code execution. In cws “networker3” this has to be adapted.

i-Team Members

	Name	E-mail Address
Specification Owner	Ingo Schmidt (is)	Ingo.Schmidt@Sun.COM
User Experience	Christian Jansen (cj)	Christian.Jansen@Sun.COM
Development	Oliver Braun (obr)	Oliver.Braun@Sun.COM
Development	Ingo Schmidt (is)	Ingo.Schmidt@Sun.COM
Development	Tino Rachui (tra)	Tino.Rachui@Sun.COM
Development	Jochen Lingner (jl)	Joachim.Lingner@Sun.COM
Quality Assurance	Olaf Felka (of)	Olaf.Felka@Sun.COM
Quality Assurance	Michael Cziebalski (mc)	Michael.Cziebalski@Sun.COM
Documentation		

Approved for Implementation

	Approved by	Date
User Experience		
Development		
Quality Assurance		
Documentation		
String Review		

Document Change History

Rev. Level	Change	Initials	Date
1.0	Initial Release	IS	20th April 04

Contents

Glossary	1

1	Motivation	1

2	Listing all Custom actions and Procedures (src680 m35)	2

3	Explanation of Procedures and Custom actions	3

4	Groups of Procedures and Custom actions	5

4.1	Unix systemintegration	6

4.2	Java	6

4.3	Adabas	6

5	Detailed Specification	6

6	Replacing the .sversionrc resp. sversion.ini (#i28291)	8

7	Process for registering MS document types (#i28276)	10

8	Package Names	11

9	Quickstarter	11

10	Legal Issues	11

11	Notes	11

12	References	12

Glossary

Term	Description
RPM	RedHat Package Manager
PKG	Solaris software package format
MSI	Microsoft Installer, old name for Windows Installer
GUI	Graphical User Interface
ESP	Easy Software Products
EPM	ESP Package Manager
SCP	Script particle, the platfrom independent installation set description language.

Motivation

After the integration of cws “newscpzip2” it is possible to create native installation sets using the new CVS module “instset_native”. The OpenOffice.org module “instsetoo_native” has still to be created due to legal issues.

The native installation sets created in “instset_native” do not offer the same functionality as corresponding installation sets created in the old cvs module “instset”. This difference is caused by specific functionality that was offered only by our old setup application. Many parts of this setup application could already be exchanged with new mechanisms in cws “newscpzip2”. There is for example the “registration of the components”, which is now already done in the build process and no longer in the installation process. Also the scp item “ConfigurationItem” which is executed in the old setup application during the installation process to write values into the configuration is done already in the build process in the new build process with native installers. Therefore the result of the cws “newscpzip2” is a StarOffice / OpenOffice.org that can be installed without problems and that can be used without finding errors immediately.

But there are still two important differences in the setup functionality. In our platform independent installation set description language scp (in the cvs module scp2 and scp2so) these two differences are described by :

Custom and Procedure

Custom actions and Procedures can be defined in scp project and are written into the setup script (setup.inf /setup.ins). Both are needed to customize the installation process. To the definition of a CustomAction belongs a library. The setup will execute the library code during the installation process. A Procedure definition contains directly the StarBasic code, that is also executed during the installation process.

Native installers have different mechanisms to allow a customization of the installation process using program code. For the Windows installer there is a complex mechanism also called “Custom Action”. There are many different types of “Custom Actions” which can be:

Execution of code saved in the Windows installer database and written in MS JSscript or MS VBScript.

Execution of files are saved as binaries in the Windows installer database

Execution of files that are newly installed

Execution of embedded installations.

The Windows installer Custom Actions are the most complex part of the Windows installer mechanism and allow nearly every thinkable customization of the installation process.

For the Unix platforms the native installer mechanisms are much more simple. Using RPMs or Solaris packages only the execution of shell scripts (preinstall, postinstall, preuninstall, postuninstall) is possible to customize the installation process.

In this cws “networker3” the code that is executed in CustomActions or in Procedures using the old setup application has to be converted into the mechanisms that are offered by the native installers. But some Procedures can also be integrated into the packaging mechanism (this happened for the Procedure gid_Procedure_Copy_Readme_File already in the cws”newscpzip2”)or are no longer needed with the native installers.

Listing all Custom actions and Procedures (src680 m35)

There are many different Custom actions and Procedures defined in the scp projects scp2 and scp2so:

c1: gid_Custom_Reg4msdoc (only Windows)

c2: gid_Custom_Regactivex (only Windows)

c3: gid_Custom_Jvm_So

c4: gid_Custom_Jvm

p1: gid_Procedure_Copy_Readme_File

p2: gid_Procedure_Remove_Readme_File

p3: gid_Procedure_Languageselect

p4: gid_Procedure_Preselect (only Windows)

p5: gid_Procedure_Start_Regsvrex (only Windows)

p6: gid_Procedure_Uninstall_Regsvrex (only Windows)

p7: gid_Procedure_Kill_Dirs

p8: gid_Procedure_Check_Uno_Packages_Standalone

p9: gid_Procedure_Check_Uno_Packages_Network

p10: gid_Procedure_Autostart_Inst (only Windows)

p11: gid_Procedure_Rename_Javaconfig

p12: gid_Procedure_Javafilter_Xmergesync_Pexcel_Reg_Install (only Windows)

p13: gid_Procedure_Javafilter_Xmergesync_Pword_Reg_Install (only Windows)

p14: gid_Procedure_Javafilter_Xmergesync_Pexcel_Reg_Uninstall (only Windows)

p15: gid_Procedure_Javafilter_Xmergesync_Pword_Reg_Uninstall (only Windows)

p16: gid_Procedure_Copy_Iso_Res (nur OOo)

p17: gid_Procedure_Python_Install (nur OOo)

p18: gid_Procedure_Copy_Bonobo_Server (only Unix)

p19: gid_Procedure_Remove_Bonobo_Server (only Unix)

p20: gid_Procedure_Install_Update_User_Mime_Data (only Unix)

p21: gid_Procedure_Deinstall_Update_User_Mime_Data (only Unix)

p22: gid_Procedure_Install_Update_User_Menus (only Unix)

p23: gid_Procedure_Deinstall_Update_User_Menus (only Unix)

p24: gid_Procedure_Patch_Font_Dir (only Unix)

p25: gid_Procedure_Remove_Jre (only Unix)

p26: gid_Procedure_Makelink_Network (only Unix)

p27: gid_Procedure_Removelink_Network (only Unix)

p28: gid_Procedure_Fixlinks (only Unix)

p29: gid_Procedure_Cde_Dtappintegrate (only Unix)

p30: gid_Procedure_Cde_Dtint (only Unix)

p31: gid_Procedure_Cde_Deinstall (only Unix)

p32: gid_Procedure_Cde_Makelinks (only Unix)

p33: gid_Procedure_Cde_Removelinks (only Unix)

p34: gid_Procedure_Remove_Cde_In_Update (only Unix)

p35: gid_Procedure_Make_Freetypelink (only Linux)

Adabas:

p36: gid_Procedure_Copy_Readme_File

p37: gid_Procedure_Remove_Readme_File

p38: gid_Procedure_Adabas_Preselectmodule

p39: gid_Procedure_Adabas_Install

p40: gid_Procedure_Adabas_Deinst

p41: gid_Procedure_Adabas_Makelink (only Unix)

Explanation of Procedures and Custom actions

c1: gid_Custom_Reg4msdoc (only Windows)

starts the "reg4msdoc680mi.dll" (TRA)

c2: gid_Custom_Regactivex (only Windows)

starts the "regactivex680mi.dll" (MAV)

c3: gid_Custom_Jvm_So

starts the "jvm680mi.dll" (JL)

c4: gid_Custom_Jvm

starts the "jvm680mi.dll" (JL)

p1: gid_Procedure_Copy_Readme_File

copies readme and license files from share/readme into the installation root

p2: gid_Procedure_Remove_Readme_File

deletes readme and license files in installation root in deinstallation process

p3: gid_Procedure_Languageselect

only for multilingual installation sets. Preselects inso modules.

p4: gid_Procedure_Preselect (only Windows)

searches for IE 5 and preselects the activex module gid_Module_Optional_Activexcontrol

p5: gid_Procedure_Start_Regsvrex (only Windows)

starts „regsvrex.exe shlxthdl.dll“

p6: gid_Procedure_Uninstall_Regsvrex (only Windows)

starts „regsvrex.exe /u shlxthdl.dll“

p7: gid_Procedure_Kill_Dirs

removes share/wordbook in deinnstallation process

p8: gid_Procedure_Check_Uno_Packages_Standalone

starts „pkgchk.exe -r -s“ and then „pkgchk.exe -r“

p9: gid_Procedure_Check_Uno_Packages_Network

starts „pkgchk.exe -r -s“

p10: gid_Procedure_Autostart_Inst (only Windows)

sets the SetFollowApplication quickstart.exe

p11: gid_Procedure_Rename_Javaconfig

for update process: java.ini -> java.ini.org

p12: gid_Procedure_Javafilter_Xmergesync_Pexcel_Reg_Install (only Windows)

setting Windows Registry for Excel javafilter

p13: gid_Procedure_Javafilter_Xmergesync_Pword_Reg_Install (only Windows)

setting Windows Registry for Word javafilter

p14: gid_Procedure_Javafilter_Xmergesync_Pexcel_Reg_Uninstall (only Windows)

removing Windows Registry for Excel javafilter

p15: gid_Procedure_Javafilter_Xmergesync_Pword_Reg_Uninstall (only Windows)

removing Windows Registry for Word javafilter

p16: gid_Procedure_Copy_Iso_Res (nur OOo)

copies ooo-resource to iso-resource

p17: gid_Procedure_Python_Install (nur OOo)

writes python.bat file

p18: gid_Procedure_Copy_Bonobo_Server (only Unix)

checking nautilus version and copying Bonobo files

p19: gid_Procedure_Remove_Bonobo_Server (only Unix)

removing Bonobo files in deinstallation process

p20: gid_Procedure_Install_Update_User_Mime_Data (only Unix)

starting "update-user-mime-data" located in the program directory

p21: gid_Procedure_Deinstall_Update_User_Mime_Data (only Unix)

starting "update-user-mime-data --remove" located in the program directory

p22: gid_Procedure_Install_Update_User_Menus (only Unix)

starting "update-user-menus" located in the program directory

p23: gid_Procedure_Deinstall_Update_User_Menus (only Unix)

starting "update-user-menus --remove" located in the program directory

p24: gid_Procedure_Patch_Font_Dir (only Unix)

creates the fonts.dir, dependent from the installed fonts

p25: gid_Procedure_Remove_Jre (only Unix)

removes the java directory inside the program directory

p26: gid_Procedure_Makelink_Network (only Unix)

creates the link /usr/bin/soffice

p27: gid_Procedure_Removelink_Network (only Unix)

removes the link /usr/bin/soffice

p28: gid_Procedure_Fixlinks (only Unix)

fixing the two broken links (after update) libsalhelper and libcppuhelper

p29: gid_Procedure_Cde_Dtappintegrate (only Unix)

cde system integration

p30: gid_Procedure_Cde_Dtint (only Unix)

cde system integration

p31: gid_Procedure_Cde_Deinstall (only Unix)

cde deinstallation

p32: gid_Procedure_Cde_Makelinks (only Unix)

cde system integration

p33: gid_Procedure_Cde_Removelinks (only Unix)

cde system integration

p34: gid_Procedure_Remove_Cde_In_Update (only Unix)

cde system integration

p35: gid_Procedure_Make_Freetypelink (only Linux)

making a link to "libfreetype.so.6"

p36: gid_Procedure_Copy_Readme_File

copies readme and license files from share/readme into the installation root in adabas installation

p37: gid_Procedure_Remove_Readme_File

deletes readme and license files in installation root in deinstallation process in adabas deinstall

p38: gid_Procedure_Adabas_Preselectmodule

checking Environ("DBROOT") for an existing Adabas installation

p39: gid_Procedure_Adabas_Install

Unix: Writing entries into .profile, .cshrc, .kshrc, .bashrc, .tcshrc

Windows: Setting some variables and editing Services-file, dependent from the Windows version

p40: gid_Procedure_Adabas_Deinst

Unix: Removing entries from .profile, .cshrc, .kshrc, .bashrc, .tcshrc

Windows: Removing the variables DBROOT, DBWORK, DBCONFIG from environment

p41: gid_Procedure_Adabas_Makelink (only Unix)

creating a link to "libncurses.so.4"

Groups of Procedures and Custom actions

The Procedures and Cutom actions can partly be separated in several groups. There are some important groups of functionality:

Adabas

Unix System integration

Java installation

The Adabas follow up installation is determined by the basic procedure

1. Unix System instegration:

p20: gid_Procedure_Install_Update_User_Mime_Data (only Unix)

p21: gid_Procedure_Deinstall_Update_User_Mime_Data (only Unix)

p22: gid_Procedure_Install_Update_User_Menus (only Unix)

p23: gid_Procedure_Deinstall_Update_User_Menus (only Unix)

p29: gid_Procedure_Cde_Dtappintegrate (only Unix)

p30: gid_Procedure_Cde_Dtint (only Unix)

p31: gid_Procedure_Cde_Deinstall (only Unix)

p32: gid_Procedure_Cde_Makelinks (only Unix)

p33: gid_Procedure_Cde_Removelinks (only Unix)

p34: gid_Procedure_Remove_Cde_In_Update (only Unix)

2. Java

c3: gid_Custom_Jvm_So

c4: gid_Custom_Jvm

p11: gid_Procedure_Rename_Javaconfig

3. Adabas

p36: gid_Procedure_Copy_Readme_File

p37: gid_Procedure_Remove_Readme_File

p38: gid_Procedure_Adabas_Preselectmodule

p39: gid_Procedure_Adabas_Install

p40: gid_Procedure_Adabas_Deinst

p41: gid_Procedure_Adabas_Makelink (only Unix)

Unix systemintegration

There is a new mechanism for the Unix system integration. Therefore all basic scripts related to this item can be removed in this CWS . The specification for the new Unix system integration mechanism can be found here:

Specification for the Unix system integration (ToDo by OBR)

Java

In StarOffice 7 and OpenOffice.org 1.x there are the Custom actions gid_Custom_Jvm_So and gid_Custom_Jvm, which use of the jvm library. A new dialog appears at 0% of the installation, in which the different Java installations are located and a new Java can be installed. Therefore we have to separate two different functionalities:

Searching for existing Java installations

Installation of Java, if the user wants it

The search for an existing Java will no longer be part of the installation. There is a new solution, in which the Office application is looking for the Java. This is described in the specification “Options Dialog/Java Panel” at http://specs.openoffice.org/appwide/index.html.

The installation of a Java, that is shipped together with StarOffice/OpenOffice.org is not clear yet (ToDo).

Adabas

Adabas shall no longer be started as follow up application.

ToDo

Detailed Specification

For every Procedure and Custom action it has to be decided, how to proceed:

Is it still required in the installation process using native installer

Can it be removed using native installer?

Can it be integrated into the packaging process?

Can it be integrated into the native installer code execution mechanisms (Shell scripts, Windows Installer Custom Actions?)

Can it be replaced by completely new mechanisms?

c1: gid_Custom_Reg4msdoc (only Windows)	i28276

c2: gid_Custom_Regactivex (only Windows)	i28277

c3: gid_Custom_Jvm_So	DONE Will be substituted by a new Java mechanism from JL

c4: gid_Custom_Jvm	DONE

Will be substituted by a new Java mechanism from JL

p1: gid_Procedure_Copy_Readme_File	DONE

Already included into the packaging process in cws newscpzip2

p2: gid_Procedure_Remove_Readme_File	DONE

Already included into the packaging process in cws newscpzip2

p3: gid_Procedure_Languageselect	116504

p4: gid_Procedure_Preselect (only Windows)	i28277

p5: gid_Procedure_Start_Regsvrex (only Windows)	i28280

p6: gid_Procedure_Uninstall_Regsvrex (only Windows)	i28280

p7: gid_Procedure_Kill_Dirs	DONE

Can be removed, not needed for native installer

p8: gid_Procedure_Check_Uno_Packages_Standalone	DONE

Already included into the packaging process in cws newscpzip2

p9: gid_Procedure_Check_Uno_Packages_Network	DONE

Already included into the packaging process in cws newscpzip2

p10: gid_Procedure_Autostart_Inst (only Windows)	i28365

p11: gid_Procedure_Rename_Javaconfig	DONE

Can be removed, not needed for native installer

p12: gid_Procedure_Javafilter_Xmergesync_Pexcel_Reg_Install (only Win)	116507

p13: gid_Procedure_Javafilter_Xmergesync_Pword_Reg_Install (only Win)	116507

p14: gid_Procedure_Javafilter_Xmergesync_Pexcel_Reg_Uninstall (only Win)	116507

p15: gid_Procedure_Javafilter_Xmergesync_Pword_Reg_Uninstall (only Win)	116507

p16: gid_Procedure_Copy_Iso_Res (nur OOo)	i28285

p17: gid_Procedure_Python_Install (nur OOo)	i28286

p18: gid_Procedure_Copy_Bonobo_Server (only Unix)	i28287

p19: gid_Procedure_Remove_Bonobo_Server (only Unix)	i28287

p20: gid_Procedure_Install_Update_User_Mime_Data (only Unix)	DONE

Can be removed because of new Unix system integration mechanism (OBR)

p21: gid_Procedure_Deinstall_Update_User_Mime_Data (only Unix)	DONE

Can be removed because of new Unix system integration mechanism (OBR)

p22: gid_Procedure_Install_Update_User_Menus (only Unix)	DONE

Can be removed because of new Unix system integration mechanism (OBR)

p23: gid_Procedure_Deinstall_Update_User_Menus (only Unix)	DONE

Can be removed because of new Unix system integration mechanism (OBR)

p24: gid_Procedure_Patch_Font_Dir (only Unix)	DONE

The patching of the file fonts.dir in no longer needed concerning to PL

p25: gid_Procedure_Remove_Jre (only Unix)	DONE

Can be removed, not needed for native installer

p26: gid_Procedure_Makelink_Network (only Unix)	i28288

p27: gid_Procedure_Removelink_Network (only Unix)	i28288

p28: gid_Procedure_Fixlinks (only Unix)	DONE

Can be removed, not needed for native installer

p29: gid_Procedure_Cde_Dtappintegrate (only Unix)	DONE

Can be removed because of new Unix system integration mechanism (OBR)

p30: gid_Procedure_Cde_Dtint (only Unix)	DONE

Can be removed because of new Unix system integration mechanism (OBR)

p31: gid_Procedure_Cde_Deinstall (only Unix)	DONE

Can be removed because of new Unix system integration mechanism (OBR)

p32: gid_Procedure_Cde_Makelinks (only Unix)	DONE Can be removed because of new Unix system integration mechanism (OBR)

p33: gid_Procedure_Cde_Removelinks (only Unix)	DONE

Can be removed because of new Unix system integration mechanism (OBR)

p34: gid_Procedure_Remove_Cde_In_Update (only Unix)	DONE

Can be removed because of new Unix system integration mechanism (OBR)

p35: gid_Procedure_Make_Freetypelink (only Linux)	i28289

p36: gid_Procedure_Copy_Readme_File	DONE

Already included into the packaging process in cws newscpzip2

p37: gid_Procedure_Remove_Readme_File	DONE

Already included into the packaging process in cws newscpzip2

p38: gid_Procedure_Adabas_Preselectmodule	116510,116511

p39: gid_Procedure_Adabas_Install	116510,116511

p40: gid_Procedure_Adabas_Deinst	116510,116511

p41: gid_Procedure_Adabas_Makelink (only Unix)	116510,116511

Replacing the .sversionrc resp. sversion.ini (#i28291)

The file .sversionrc (sversion.ini for Windows) is a file created during the installation process by the old setup application. It contains key-value pairs, where the key describs the installed product and the value is the path to the Office installation. The setup application used this file for the maintenance mode, for patch and update mechanisms. In a central place (the user home directory) the path to the application could be found. In the past years additional applications used this file, to detect the Office application, for example the testtool.

Using native installers, this sversion-file is no longer created automatically. Therefore an alternative for this file is needed. This is the following mechanism:

Windows:

The Windows registry contains the following new entries.

StarOffice/StarSuite:

RegistryItem gid_Regitem_Software_Sun_Microsystems_Productname_Productversion_Path

ParentID = PREDEFINED_HKEY_LOCAL_MACHINE;

Subkey = "Software\Sun Microsystems\%PRODUCTNAME\%PRODUCTVERSION";

ModuleID = gid_Module_Root;

Name = "Path";

Value = "<progpath>\program\soffice.exe";

End

This RegistryItem expands to “Software\Sun Microsystems\StarOffice\8” and contains a key “Path” and the value to the “soffice.exe”. The key is written below HKEY_LOCAL_MACHINE or below HKEY_CURRENT_USER, this is dependent from the user settings durings the installation process and the user privileges.

OpenOffice.org

RegistryItem gid_Regitem_Software_Openoffice_Productname_Productversion_Path

ParentID = PREDEFINED_HKEY_LOCAL_MACHINE;

Subkey = "Software\OpenOffice.org\%PRODUCTNAME\%PRODUCTVERSION";

ModuleID = gid_Module_Root;

Name = "Path";

Value = "<progpath>\program\soffice.exe";

End

This RegistryItem expands to “Software\OpenOffice.org\OpenOffice.org\2.0” and contains a key “Path” and the value to the “soffice.exe”. The key is written below HKEY_LOCAL_MACHINE or below HKEY_CURRENT_USER, this is dependent from the user settings durings the installation process and the user privileges.

Unix:

A root installation always creates the link /usr/bin/soffice, that can be used to find the office installation. For a non-root installation (with rpm -i –dbpath –relocate) no simple mechanism is possible. The person installing the soffice as non root has to create a link, for example in the user home directory, to find the soffice (i29341, not part of cws networker3). After –relocate a shell script cannot create a correct link, because the relocate path is not available in shell scripts. But for the non-root installing person, the link creation is very simple (this is relevant for the Testtool).

Process for registering MS document types (#i28276)

A substitute has to be found for the process in which Microsoft document types could be registered to StarOffice / OpenOffice.org using the old setup application. Using the Windows installer a new dialog has to be created using the corresponding Windows installer databases. In this dialog the user can select, for which document types StarOffice / OpenOffice.org shall be registered. The dialog which uses only strings that were already used in the old setup application is show here:

The variables for the checkboxes are named: SELECT_WORD, SELECT_EXCEL, and SELECT_POWERPOINT.

Two Windows Installer CustomActions are created. The first is executed before the dialog is shown and sets the default values. The second CustomAction is executed at the end of the installation and makes the registration concerning to the settings of the dialog. There still might be problems, if a user presses the Cancel Button. Probably we will need a Rollback script for this, but this will be fixed after SO 8 EA.

Package Names

The package names (Solaris-Packages and RPMs) are defined concerning to the following rules:

No PRODUCTVERSION in packagename. For RPMs the productversion is automatically included into the rpm file name.

Solaris: SUNWstaroffice-core.pkg

Linux: SUNWstaroffice-core-8-0.i586.rpm

The fact that there is no productversion in the package name is relevant to the update process. This makes it possible, that a StarOffice 9 will update an StarOffice 8. Without the productversion in the package name both could be installed next to each other.

No limitation to 9 letter for Solaris packages. JDS uses 25 letters, we want to use it, too (SUNWstaroffice-core.pkg).

Addition “-core” for the root module (SUNWstaroffice-core.pkg).

OpenOffice package names for Solaris start with OOO: OOOopenoffice.org-writer

The RPMS have the same names as the Solaris packages. But additionally Solaris packages use the prefix with SUNW or RPM.

Quickstarter

Because of technical problems with the quickstarter and the license dialog, product management (LHO and FL) decided that for SO 8 EA the setup shall no longer start the quickstarter. Starting the quickstarter causes that the License dialog appears, if the Office is started for the first time. It is very difficult for the soffice, to detect, whether the Office shall be startet with GUI or only the quickstarter shall be started. Therefore the following solution was found:

The setup does not start the quickstarter and does not write the corresponding Shortcut into the Autostart folder. Therefore there is no Office start (no quickstarter start) at the end of the installation and the License dialog does not appear.

Therefore the user has to start the Office and gets, if this is his first Office start, the License dialog. If he accepts the license, the quickstarter ist started and the Shortcut is written into the Autostart folder (always).

Legal Issues

Windows Installer, the legal review is still pending.

Hosting parts of Windows Installer database tables on OpenOffice.org

EPM (Open Source)

Windows Installer SDK

Notes

References

Documentation of scp projects:

http://staroffice-doc.germany.sun.com:8080/Projects/Common/Documentation/Developer_Docs/How_to_Scp/how_to_scp.html

ESP Package Manager:

http://www.easysw.com/epm/

Windows Installer SDK:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/about_windows_installer.asp

Windows Installer:

Inside Windows Installer, Andreas Kerl, Microsoft Press, 2003

The Official InstallShield for Windows Installer Developer's Guide, Bob Baker, M&T Books, 2000

<networker3>

Page 1

2003-10-07T15:20:14