incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1175543 [1/2] - /incubator/ooo/ooo-site/trunk/content/installation/
Date Sun, 25 Sep 2011 19:40:35 GMT
Author: kschenk
Date: Sun Sep 25 19:40:34 2011
New Revision: 1175543

URL: http://svn.apache.org/viewvc?rev=1175543&view=rev
Log:
KLS - added installation repository

Added:
    incubator/ooo/ooo-site/trunk/content/installation/
    incubator/ooo/ooo-site/trunk/content/installation/01RESPONSE_SO52_final_rev2.pdf   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/How_to_scp_in_ooo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/Java_GUI_Installer.odt   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/Java_GUI_Installer_Quick_Guide.odt   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/epm-3.7.patch   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/how_to_create_native_installer.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_oo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_so.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/how_to_scp_oo.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/index.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/red.html   (with props)
    incubator/ooo/ooo-site/trunk/content/installation/robots.txt   (with props)

Added: incubator/ooo/ooo-site/trunk/content/installation/01RESPONSE_SO52_final_rev2.pdf
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/01RESPONSE_SO52_final_rev2.pdf?rev=1175543&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/installation/01RESPONSE_SO52_final_rev2.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Added: incubator/ooo/ooo-site/trunk/content/installation/How_to_scp_in_ooo.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/How_to_scp_in_ooo.html?rev=1175543&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/How_to_scp_in_ooo.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/How_to_scp_in_ooo.html Sun Sep 25 19:40:34 2011
@@ -0,0 +1,69 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE></TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 8  (Solaris Sparc)">
+	<META NAME="AUTHOR" CONTENT="Ingo Schmidt">
+	<META NAME="CREATED" CONTENT="20020419;13085671">
+	<META NAME="CHANGED" CONTENT="20070730;17312200">
+</HEAD>
+<BODY LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT SIZE=6>How
+to scp in OpenOffice.org?</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Understanding
+the principles of the scp project is important for everyone, who
+makes changes, which concern the installation set. Adding a new file
+or changing an entry in the Windows registry are typical examples,
+which make necessary changes in one of the scp projects. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+scp projects are important for creating the setup script files, which
+can be found in the installation set next to the setup executable
+file. The name of the setup scripts is normally setup.inf for the
+Windows platform and setup.ins for Unix platforms.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">This
+(of course not complete) introduction describes the user in different
+steps his daily work with the scp projects. Everyone who never worked
+with scp, should read the file</FONT></P>
+<P><A HREF="pics/understanding_the_scp_project.html"><FONT FACE="Verdana, sans-serif">Understanding
+the scp projects</FONT></A></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">to
+get a better understanding of the different scp projects, the build
+mechanisms and the possibilities inside this projects. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+script language is described for an example file in the document</FONT></P>
+<P><A HREF="pics/understanding_the_scipt_language.html"><FONT FACE="Verdana, sans-serif">Understanding
+the script language</FONT></A></P>
+<P><FONT FACE="Verdana, sans-serif">All elements, which can be
+defined in the scp projects, like <A HREF="pics/scpitem_file.html">Files</A>,
+<A HREF="pics/scpitem_directory.html">Directories</A>, <A HREF="pics/scpitem_unixlink.html">Unixlinks</A>,
+... are explained in the page</FONT></P>
+<P><A HREF="pics/understanding_the_scipt_elements.html"><FONT FACE="Verdana, sans-serif">Understanding
+the script elements</FONT></A></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">This
+is a very detailed explanation of the scripting language and allows a
+very good understanding of the complete setup script. </FONT>
+</P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">The
+meaning of the lng files, which are important for translation
+reasons, in the scp projects is described in </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="pics/understanding_the_lng_files.html">Understanding
+the lng files</A>.</FONT></P>
+<P STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif">Additional information about the
+patch creation using the flag "PATCH" is described in </FONT>
+<FONT FACE="Verdana, sans-serif"><A HREF="pics/understanding_the_patch_flag.html">Understanding
+the PATCH flag</A>.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Two important concepts in the scp
+projects are the <A HREF="pics/automatical_assignments.html">automatical
+assignment</A> of global IDs to modules (including the removal of
+undefined global IDs from modules) and the <A HREF="pics/undefining_gids.html">undefining
+of global IDs</A>.</FONT></P>
+<P><BR><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/How_to_scp_in_ooo.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/Java_GUI_Installer.odt
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/Java_GUI_Installer.odt?rev=1175543&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/installation/Java_GUI_Installer.odt
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/ooo/ooo-site/trunk/content/installation/Java_GUI_Installer.odt
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ooo/ooo-site/trunk/content/installation/Java_GUI_Installer_Quick_Guide.odt
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/Java_GUI_Installer_Quick_Guide.odt?rev=1175543&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/installation/Java_GUI_Installer_Quick_Guide.odt
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/ooo/ooo-site/trunk/content/installation/Java_GUI_Installer_Quick_Guide.odt
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ooo/ooo-site/trunk/content/installation/epm-3.7.patch
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/epm-3.7.patch?rev=1175543&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/epm-3.7.patch (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/epm-3.7.patch Sun Sep 25 19:40:34 2011
@@ -0,0 +1,150 @@
+*** misc/epm-3.7/epm.c	Tue Oct 28 15:48:30 2003
+--- misc/build/epm-3.7/epm.c	Tue Jun  8 11:02:35 2004
+***************
+*** 547,552 ****
+--- 547,553 ----
+  {
+    puts(EPM_VERSION);
+    puts("Copyright 1999-2003 by Easy Software Products.");
++   puts("Patched for OpenOffice.org");
+    puts("");
+    puts("EPM is free software and comes with ABSOLUTELY NO WARRANTY; for details");
+    puts("see the GNU General Public License in the file COPYING or at");
+*** misc/epm-3.7/pkg.c	Tue Dec 17 19:57:56 2002
+--- misc/build/epm-3.7/pkg.c	Mon May  3 19:33:04 2004
+***************
+*** 429,503 ****
+  
+    fclose(fp);
+  
+-  /*
+-   * Build the distribution from the prototype file...
+-   */
+- 
+-   if (Verbosity)
+-     puts("Building PKG binary distribution...");
+- 
+-   if (run_command(NULL, "pkgmk -o -f %s/%s.prototype -d %s/%s",
+-                   directory, prodname, current, directory))
+-     return (1);
+- 
+-  /*
+-   * Tar and compress the distribution...
+-   */
+- 
+-   if (Verbosity)
+-     puts("Creating tar.gz file for distribution...");
+- 
+-   snprintf(filename, sizeof(filename), "%s/%s.tar.gz", directory, name);
+- 
+-   if ((tarfile = tar_open(filename, 1)) == NULL)
+-     return (1);
+- 
+-   snprintf(filename, sizeof(filename), "%s/%s", directory, prodname);
+- 
+-   if (tar_directory(tarfile, filename, prodname))
+-   {
+-     tar_close(tarfile);
+-     return (1);
+-   }
+- 
+-   tar_close(tarfile);
+- 
+-  /*
+-   * Make a package stream file...
+-   */
+- 
+-   if (Verbosity)
+-     puts("Copying into package stream file...");
+- 
+-   if (run_command(directory, "pkgtrans -s %s/%s %s.pkg %s",
+-                   current, directory, name, prodname))
+-     return (1);
+- 
+-  /*
+-   * Remove temporary files...
+-   */
+- 
+-   if (!KeepFiles)
+-   {
+-     if (Verbosity)
+-       puts("Removing temporary distribution files...");
+- 
+-     snprintf(filename, sizeof(filename), "%s/%s.pkginfo", directory, prodname);
+-     unlink(filename);
+-     snprintf(filename, sizeof(filename), "%s/%s.depend", directory, prodname);
+-     unlink(filename);
+-     snprintf(filename, sizeof(filename), "%s/%s.prototype", directory, prodname);
+-     unlink(filename);
+-     if (preinstall[0])
+-       unlink(preinstall);
+-     if (postinstall[0])
+-       unlink(postinstall);
+-     if (preremove[0])
+-       unlink(preremove);
+-     if (postremove[0])
+-       unlink(postremove);
+-   }
+- 
+    return (0);
+  }
+  
+--- 429,434 ----
+*** misc/epm-3.7/rpm.c	Wed Oct  1 21:27:15 2003
+--- misc/build/epm-3.7/rpm.c	Mon May  3 19:33:04 2004
+***************
+*** 415,467 ****
+      }
+    }
+  
+-  /*
+-   * Build the distribution from the spec file...
+-   */
+- 
+-   if (Verbosity)
+-     puts("Building RPM binary distribution...");
+- 
+-   if (strcmp(platform->machine, "intel") == 0)
+-   {
+-     if (run_command(NULL, EPM_RPMBUILD " %s -bb " EPM_RPMARCH "i386 %s",
+-                     Verbosity == 0 ? "--quiet" : "", specname))
+-       return (1);
+-   }
+-   else if (run_command(NULL, EPM_RPMBUILD " %s -bb " EPM_RPMARCH "%s %s",
+-                        Verbosity == 0 ? "--quiet" : "", platform->machine,
+- 		       specname))
+-     return (1);
+- 
+-  /*
+-   * Move the RPM to the local directory and rename the RPM using the
+-   * product name specified by the user...
+-   */
+- 
+-   if (strcmp(platform->machine, "intel") == 0)
+-     run_command(NULL, "/bin/mv %s/RPMS/i386/%s-%s-%d.i386.rpm %s/%s.rpm",
+-         	rpmdir, prodname, dist->version, dist->relnumber,
+- 		directory, name);
+-   else
+-     run_command(NULL, "/bin/mv %s/RPMS/%s/%s-%s-%d.%s.rpm %s/%s.rpm",
+-         	rpmdir, platform->machine, prodname, dist->version,
+- 		dist->relnumber, platform->machine, directory, name);
+- 
+-  /*
+-   * Remove temporary files...
+-   */
+- 
+-   if (!KeepFiles)
+-   {
+-     if (Verbosity)
+-       puts("Removing temporary distribution files...");
+- 
+-     run_command(NULL, "/bin/rm -rf %s/RPMS", directory);
+-     run_command(NULL, "/bin/rm -rf %s/buildroot", directory);
+- 
+-     unlink(specname);
+-   }
+- 
+    return (0);
+  }
+  
+--- 415,420 ----

Propchange: incubator/ooo/ooo-site/trunk/content/installation/epm-3.7.patch
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/how_to_create_native_installer.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/how_to_create_native_installer.html?rev=1175543&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/how_to_create_native_installer.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/how_to_create_native_installer.html Sun Sep 25 19:40:34 2011
@@ -0,0 +1,208 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
+	<TITLE></TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 7  (Win32)">
+	<META NAME="CREATED" CONTENT="20040628;10483376">
+	<META NAME="CHANGED" CONTENT="20040628;14315971">
+</HEAD>
+<BODY LANG="de-DE" DIR="LTR">
+<P><FONT SIZE=5><B>HowTo create native installation sets for
+OpenOffice.org 2.x<BR></B></FONT><BR><BR>
+</P>
+<P>by <A HREF="mailto:is@openoffice.org">Ingo Schmidt</A></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4><BR>Introduction:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">This HowTo describes the necessary
+steps to create native installation sets for OpenOffice.org 2.0. This
+includes Windows Installer for the Windows platform, RPMs for Linux
+and Solaris-packages for Solaris. Because of the usage of EPM is will
+also be possible to create native installation sets for all operating
+systems supported by EPM. In the current EPM version 3.7 this are:
+AIX, FreeBSD, NetBSD, OpenBSD, HP-UX, Debian software distribution,
+IRIX, MacOS X. The currently available process is adapted to Windows,
+Linux and Solaris. Therefore it might be necessary to make some
+changes in the new packaging process for the other platforms. The
+installation sets are created in the new cvs module
+&bdquo;instsetoo_native&ldquo;, but it is also still possible to
+create installation sets using the old setup application in the cvs
+module &bdquo;instsetoo&ldquo;. But in the near future we want to
+remove the module &bdquo;instsetoo&ldquo; and with it the old setup
+application located in the cvs module &bdquo;setup2&ldquo;</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>The packaging program:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">New CVS modules were introduced for the
+usage of native installer. This are &bdquo;setup_native&ldquo; and
+&bdquo;instsetoo_native&ldquo;. Additionally the packaging program
+was added to the &bdquo;solenv&ldquo; module. 
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>&bdquo;solenv&ldquo;</U>: The new
+packaging program is completely Perl based. You find it in
+solenv/bin. The main program is called &bdquo;make_installer.pl&ldquo;.
+It uses all the Perl submodules located in
+solenv/bin/modules/installer.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>&bdquo;setup_native&ldquo;</U>: This
+new cvs module contains at the moment the Windows Installer custom
+actions, that are executed during the installation process.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>&bdquo;instsetoo_native&ldquo;</U><SPAN STYLE="text-decoration: none">:
+This is the new packaging module. In the output tree of
+&bdquo;instsetoo_native&ldquo; the installation sets are created. You
+will find there also a preregistered services.rdb, many unpacked zip
+files, logging files and many files more. Therefore you need
+sufficient disc space for the &bdquo;instsetoo_native&ldquo;
+directory. This shows that the new packaging process includes much
+functionality, that was included in our old setup application, but is
+not supported by the native installers. Therefore is also takes more
+time to create the native installation sets, but we are still trying
+to optimize this process.</SPAN></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>The packaging process:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Included in the new packaging process
+are different Perl programs, that create the native installation sets
+based on the information stored in our platform independent
+installation set description language &bdquo;scp&ldquo;. Files,
+directories, and many things more are described in the cvs module
+&bdquo;scp2&ldquo;. Based on these files, a platform and product
+specific setup script is created, which is then used by the new
+packaging process to create the native installation sets. The
+different processes are shown in the following graphic:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><IMG SRC="pics/how_to_create_native_installer.gif" NAME="Grafik1" ALIGN=LEFT WIDTH=571 HEIGHT=408 BORDER=0><BR CLEAR=LEFT><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>Prerequisites:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">For the new native packaging process,
+new prerequisites are needed. Especially there are different
+prerequisites for the Windows OS and the non-Windows OS:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>Windows</U>: For creating
+successfully Windows Installer installation sets it is needed, that
+you have installed the Windows Plattform SDK with Windows Installer
+SDK, Version February 2003. This is available at
+<A HREF="http://www.microsoft.com/msdownload/platformsdk/sdkupdate/">http://www.microsoft.com/msdownload/platformsdk/sdkupdate/</A>
+.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The two Windows Installer files
+instmsia.exe and instmsiw.exe (non-Unicode and Unicode version of the
+Windows Installer service) have also to be downloaded from the
+Microsoft homepage. For the packaging process they have to be located
+in the directory &bdquo;instsetoo_native/inc_openoffice/windows/msifiles&ldquo;.
+This will probably change in the near future.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>Non-Windows</U>:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">For the non-Windows platforms it is
+essential, that you have installed EPM, v. 3.7 on your system. You
+can download it from <A HREF="http://www.easysw.com/epm/">http://www.easysw.com/epm/</A></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Using EPM for Linux or Solaris we
+approve the usage of a patch, that can be downloaded <A HREF="epm-3.7.patch">here</A>.
+This patch fixes the following problems:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">The RPMs or Solaris packages are
+relocatable. This means, that the administrator can change the
+OpenOffice.org installation directory. Non relocatable RPMs or
+Solaris packages are always installed at a fixed place in the
+directory system. In the version 4.0 of EPM it is planned, to make
+the packages relocatable, then this patch becomes superfluous.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">A second problem occurs only on Linux
+and is caused by some dependency problems of the OpenOffice.org
+libraries. Without the patch the OpenOffice.org core RPM can only be
+installed with the parameter &bdquo;--nodeps&ldquo;. If you use the
+patch, you can simply install &bdquo;rpm -i
+openoffice-core-680-1.i586.rpm&ldquo;.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Using Solaris 8 and Solaris 9 maximum
+package name contains 9 characters. Because this is not sufficient
+for for the different OpenOffice.org packages, we decided to make use
+of Bug 4025718, which introduces the maximum of 25 characters for a
+package name. This requires that the following patches are installed
+on Solaris systems:</P>
+<P STYLE="margin-bottom: 0cm"><BR>The longer packages names we
+introduce by Bug 4025718. <BR>If your building packages on Solaris 8
+you need patches: <BR>110934-12 (sparc) &amp; 110935-12 (x86) <BR>If
+your building packages on Solaris 9 you need patches: <BR>113713-03
+(sparc) &amp; 114568-02 (x86) 
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>Installation of native
+installation sets:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><U>Windows:</U> The installation set is
+located in the directory
+instsetoo_native/wntmsci10.pro/OpenOffice/install . You find there an
+executable &bdquo;setup.exe&ldquo;, which you can simply start. Then
+you get the well-known Windows Installer GUI that will guide you
+through the installation process. The OpenOffice.org can only be
+removed with the &bdquo;Add-Remove-Software-Applet&ldquo;, that is
+located in the Control Panel.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P><U>Linux</U>: The installation set is located in the directory
+instsetoo_native/unxlngi5.pro/OpenOffice/install . You find there
+different RPMs belonging to the installation set. You can decide
+wheter you want to install all of them or only parts. The names of
+the RPMs are not fix yet. First of all you have to install the core
+RPM openoffice-core-680-1.i586.rpm. All other RPMs have a dependency
+to this core package. For installing a RPM you need to have root
+priviliges. Than you can simply install it by :</P>
+<P>rpm -i openoffice-core-680-1.i586.rpm --prefix=/opt/myOOOdir
+(relocatable with the optional parameter --prefix) 
+</P>
+<P>Without using the EPM patch, you also have to use the parameter
+&bdquo;--nodeps&ldquo;.</P>
+<P>You can remove the RPM with the command (this is also system
+dependent)</P>
+<P>rpm -e openoffice-core-680-1.i586.rpm</P>
+<P><U>Solaris</U>: The installation set is located in the directory
+instsetoo_native/unxsols4.pro/OpenOffice/install
+(instsetoo_native/unxsoli4.pro/OpenOffice/install for Solaris x86) .
+You find there different Solaris packages belonging to the
+installation set. You can decide wheter you want to install all of
+them or only parts. The names of the packages are not fix yet. First
+of all you have to install the core package OOOopenoffice-core. All
+other packages have a dependency to this core package. For installing
+a Solaris package you need to have root priviliges. Than you can
+simply install it by :</P>
+<P>pkgadd -a adminfile.txt -d . OOOopenoffice-core (relocatable with
+the optional admin file (parameter -a) in which
+&quot;basedir=/opt/myOOOdir&quot; has to be defined) 
+</P>
+<P>You can remove the Solaris package with the command:</P>
+<P>pkgrm OOOopenoffice-core</P>
+<P><BR><BR>
+</P>
+<P>And now have fun with the native installer :-)</P>
+<P><BR><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

Propchange: incubator/ooo/ooo-site/trunk/content/installation/how_to_create_native_installer.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_oo.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_oo.html?rev=1175543&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_oo.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_oo.html Sun Sep 25 19:40:34 2011
@@ -0,0 +1,165 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+  	   
+  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=iso-8859-1">
+  <title></title>
+     	 	   
+  <meta name="GENERATOR" content="StarOffice/5.2 (Win32)">
+  	   
+  <meta name="AUTHOR" content="Oliver Bolte">
+  	   
+  <meta name="CREATED" content="20001218;17461754">
+  	   
+  <meta name="CHANGEDBY" content="Ingo Schmidt">
+  	   
+  <meta name="CHANGED" content="20010205;15392152">
+  	   
+  <style>
+	<!--
+		@page { margin: 2cm }
+	-->
+	</style>
+</head>
+  <body>
+   
+<p align="Center" style="margin-bottom: 0cm;"><b><font size="5">HowTo repackage 
+an OpenOffice.org installation set<br>
+ </font></b><font size="5"><small><small>by </small></small></font><b><font size="5"><small><small><a href="mailto:Oliver.Braun@sun.com">
+ Oliver Braun</a></small></small><br>
+ </font></b></p>
+ 
+<p align="Center" style="margin-bottom: 0cm;"></p>
+ 
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+ Introduction:</font></p>
+   
+<p style="margin-bottom: 0cm;"><span style="font-weight: medium"></span></p>
+   
+<p style="margin-bottom: 0cm;"> </p>
+   
+<p style="margin-bottom: 0cm;">This HowTo describes the necessary steps to 
+take to be able to make standard unix packages (rpm, pkg, ..) out of an OpenOffice.org 
+installation set. It does not deal with any specific package manager. If you
+have created a script for your favourite package manager and want to share
+it with others, please drop me a <a href="mailto:Oliver.Braun@sun.com?subject=package%20manager%20script">
+ note</a>.</p>
+ 
+<p style="margin-bottom: 0cm;">The&nbsp;OpenOffice.org     641 B/C installation
+on a unix system differs slightly from an&nbsp;StarOffice<small><sup>TM</sup></small>
+         6.0 installation, so if you are looking for instructions for the
+last     one, you should look <a href="how_to_repackage_so.html">here</a>
+. The most obvious difference between OpenOffice and StarOffice<small><sup>
+TM</sup></small>         6.0&nbsp;is the missing menu integration for KDE
+and GNOME. Before copying the this integration to the OpenOffice.org installation
+sets it should be made clear if the OpenOffice.org community likes the document
+centric approach of the panel menus and if it wants to create an own set
+of icons or to stick with that ones provided for StarOffice<small><sup>TM</sup></small>
+.&nbsp;</p>
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+        A. Install OpenOffice on your machine</font></p>
+<ol>
+  <li>
+    <p style="margin-bottom: 0cm;">Log into your machine as <b>root</b>.&nbsp;</p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0cm;">Start the setup application with the "-net"
+    option: <b>&lt;path-to-office-installation-set&gt;/setup -net &amp;</b><br>
+    </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0cm;">On the "Select Installation Type" page,
+   select "<b>Custom Installation</b>".</p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0cm;">On the "Select OpenOffice641 Modules" 
+ page open the node "<b>Optional Components</b>" and&nbsp;<br>
+a) de-select "Java Environment Installation" if you want to detect/select 
+  the java version yourself.<br>
+     </p>
+  </li>
+  <li>
+    <p style="margin-bottom: 0cm;">Choose the directory to install to, e.g.
+      <b>/opt/OpenOffice641</b>, and install.<br>
+    <br>
+    </p>
+  </li>
+</ol>
+<p style="margin-bottom: 0cm;"><font size="4">B. Create the package file
+list(s)</font></p>
+<p style="margin-bottom: 0cm;">Before you start to scan the directory tree
+  you should decide if you want to create one single package containing all
+  files or if you prefer two packages, a binary and a language one. The second
+  way has the advantage of saving a log of disk space if you are going to
+provide  packages for different languages on the same disc.</p>
+<p style="margin-bottom: 0cm;">To split the file list into two, you should
+  include all files in <b>&lt;path-to-openoffice-root&gt;/program/resource</b>
+     and the <b>&lt;path-to-openoffice-root&gt;/share</b> tree into &nbsp;the
+  language package list and the rest into the binary package list.</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><font size="4">C. GNOME 1.4 integration</font></p>
+<p style="margin-bottom: 0cm;">StarOffice<small><sup>TM</sup></small><font size="3">
+ 6.0 comes with a user space GNOME 1.4 integration that consists of  a set
+of zip files containing the menu integration files and a small binary   that
+does the user space filetype registration. As you may want the GNOME   integration
+to be system wide, you can only take the corresponding files  as templates,
+but have to provide your own set of files.</font></p>
+<p style="margin-bottom: 0cm;"><font size="3">To find the files provided
+by </font>StarOffice<small><sup>TM</sup></small><font size="3"> you will
+have an OpenOffice.org build tree available. You should find the following
+two sets of zip files in the output tree of a successful OpenOffice build:&nbsp;
+ group_pngs.zip, writer_pngs.zip, calc_pngs.zip, draw_pngs.zip, impress_pngs.zip
+ (containing the icons) and gnomeappgroup.zip, gnomeappwriter.zip, gnomeappcalc.zip,
+ gnomeappdraw.zip, gnomeappimpress.zip (cntaining the .desktop templates).&nbsp;</font></p>
+<p style="margin-bottom: 0cm;"><font size="3">If you want to register </font>
+   the OpenOffice<font size="3"> file types, you  may will find a list of
+them <a href="http://framework.openoffice.org/documentation/mimetypes/mimetypes.html">
+   here</a>.&nbsp; Note that there is currently a problem with Nautilus 1.x 
+ with the XML file formats: Nautilus recognizes them as zip files (which is
+ correct), but does not offer a way to override this detection result for
+specific extensions.</font></p>
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+   D. GNOME 2 integration</font></p>
+<p style="margin-bottom: 0cm;"><font size="3">In the upcoming 2.0 release 
+ </font>GNOME will probably switch to UTF-8 encoding for the NLS strings in
+ the .desktop file, so you may use the KDE integration files as templates.<br>
+</p>
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+   E. KDE integration<br>
+</font><font size="3"><br>
+</font><font size="3">StarOffice<small><sup>TM</sup></small></font><font size="3">
+ 6.0 comes with a user space KDE 2.x integration that consists  of two sets
+of zip files containing the menu integration files and the mime  registration
+files. These files contain a bunch of placeholders you will have to replace
+before using the files. You may also think about changing the menu structure
+from being document based to be apllication based for the document based
+structure has the following drawbacks: One sees a document  (e.g. Textdocument)
+in the "Open with" list of the context menu of a</font>   StarOffice<small><sup>
+TM</sup></small> file and the application launch feedback also names the
+document instead of the application.</p>
+<p style="margin-bottom: 0cm;"><font size="3">To find the files provided
+by </font>StarOffice<small><sup>TM</sup></small><font size="3"> </font><font size="3">
+you will have an OpenOffice.org build tree available. You should find the
+following two sets of zip files in the output tree of a successful OpenOffice
+build:</font><font size="3"> kdeappgroup.zip, kdeappwrite.zip, kdeappcalc.zip,
+kdeappdraw.zip,  kdeappimpress.zip (containing the menu .desktop templates)
+and kdeappgroup.zip, kdeappwriter.zip,  kdeappcalc.zip, kdeappdraw.zip, kdeappimpress.zip
+(containing the icons and the file  type registration files).&nbsp;</font></p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><font size="4">F. Java setup</font></p>
+<p style="margin-bottom: 0cm;">coming soon ..<br>
+</p>
+<p style="margin-bottom: 0cm;"><br>
+</p>
+<p style="margin-bottom: 0cm; text-decoration: none;"><br>
+</p>
+<p style="margin-bottom: 0cm;"><br>
+ </p>
+ 
+<p style="margin-bottom: 0cm; text-decoration: none;"><br>
+  </p>
+   
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_oo.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_so.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_so.html?rev=1175543&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_so.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_so.html Sun Sep 25 19:40:34 2011
@@ -0,0 +1,214 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<html>
+<head>
+         	                        
+  <meta http-equiv="CONTENT-TYPE" content="text/html; charset=iso-8859-1">
+  <title></title>
+                                 	 	                        
+  <meta name="GENERATOR" content="StarOffice/5.2 (Win32)">
+         	                        
+  <meta name="AUTHOR" content="Oliver Bolte">
+         	                        
+  <meta name="CREATED" content="20001218;17461754">
+         	                        
+  <meta name="CHANGEDBY" content="Ingo Schmidt">
+         	                        
+  <meta name="CHANGED" content="20010205;15392152">
+         	                        
+  <style>
+	<!--
+		@page { margin: 2cm }
+	-->
+	</style>
+</head>
+  <body>
+                 
+<p align="Center" style="margin-bottom: 0cm;"><b><font size="5">HowTo repackage
+    an StarOffice<small><small><sup>TM</sup></small></small> installation
+set<br>
+        </font></b><font size="5"><small><small>by <b><a href="mailto:Oliver.Braun@sun.com">
+        Oliver Braun</a></b></small></small><b><br>
+        </b></font></p>
+                  
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+        Introduction:</font></p>
+                      
+<p style="margin-bottom: 0cm;"> </p>
+                 
+<p style="margin-bottom: 0cm;">This HowTo describes the necessary steps to
+    take to be able to make standard unix packages (rpm, pkg, ..) out of
+an   StarOffice<small><sup>  TM</sup></small> installation set. It does not
+deal   with any specific package manager. If you have created a script for
+your  favourite package manager and want to share it with others, please
+drop me  a <a href="mailto:Oliver.Braun@sun.com?subject=package%20manager%20script">
+        note</a>.</p>
+               
+<p style="margin-bottom: 0cm;">The StarOffice<small><sup>TM</sup></small>
+        6.0 installation on a unix system differs slightly from an OpenOffice.org 
+   641 B/C installation, so if you are looking for instructions for the last 
+   one, you should look <a href="how_to_repackage_oo.html">here</a>.&nbsp;</p>
+             
+<p style="margin-bottom: 0cm;"> </p>
+               
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+       A. Install StarOffice<small><sup>TM</sup></small> &nbsp;on your machine</font></p>
+                    
+<ol>
+         <li>                                        
+    <p style="margin-bottom: 0cm;">Log into your machine as <b>root</b>.&nbsp;</p>
+         </li>
+         <li>                                   
+    <p style="margin-bottom: 0cm;">Start the setup application with the "-net" 
+   option: <b>&lt;path-to-office-installation-set&gt;/setup -net &amp;</b><br>
+           </p>
+         </li>
+         <li>                                        
+    <p style="margin-bottom: 0cm;">On the "Select Installation Type" page, 
+  select "<b>Custom Installation</b>".</p>
+         <i>                 </i></li>
+       <li>                         
+    <p style="margin-bottom: 0cm;">On the "Select StarOffice 6.0 Modules"
+  page open the node "<b>Optional Components</b>" and&nbsp;<br>
+    a) de-select "Adabas Database" for this is not covered by this HowTo
+yet.<br>
+    b) de-select "Java Environment Installation" if you want to detect/select
+  the java version yourself.<br>
+    c) de-select "CDE Integration" (default on Linux) even if you want the
+ integration  to be included in your package.<br>
+    d) de-select "GNOME Integration" (default on Solaris) if you want to
+do  the GNOME 1.4 integration yourself.<br>
+    e) <b>Linux only</b>: de-select "KDE Integration" if you want to do the 
+ KDE 2 integration yourself.<br>
+        </p>
+        </li>
+          <li>                                        
+    <p style="margin-bottom: 0cm;">Choose the directory to install to, e.g. 
+     <b>/opt/staroffice6.0</b>, and install.<br>
+       <br>
+       </p>
+                                    </li>
+     
+</ol>
+                            
+<p style="margin-bottom: 0cm;"><font size="4">B. Create the package file list(s)</font></p>
+                    
+<p style="margin-bottom: 0cm;">      </p>
+                
+<p style="margin-bottom: 0cm;">Before you start to scan the directory tree 
+ you should decide if you want to create one single package containing all 
+ files or if you prefer two packages, a binary and a language one. The second 
+ way has the advantage of saving a lot of disk space if you are going to provide
+ packages for different languages on the same disc.</p>
+     
+<p style="margin-bottom: 0cm;">To split the file list into two, you should 
+ include all files in <b>&lt;path-to-staroffice-root&gt;/program/resource</b>
+    and the <b>&lt;path-to-staroffice-root&gt;/share</b> tree into &nbsp;the 
+ language package list and the rest into the binary package list.</p>
+     
+<p style="margin-bottom: 0cm;">Note: if you don't want a CDE integration at
+all, you can remove the <b>&lt;path-to-staroffice-root&gt;/share/cde</b> 
+ subtree from your installation before creating the file lists.<br>
+   <br>
+   </p>
+                                                                       
+<p style="margin-bottom: 0cm;"><font size="4">C. CDE integration</font></p>
+                 
+<p style="margin-bottom: 0cm;">StarOffice<small><sup>TM</sup></small> supports 
+ two different ways to integrate with your CDE: &nbsp;a system wide panel 
+integration and a user based fallback. In our senario the user based fallback 
+will not work because we have deselected CDE integration during the setup.</p>
+     
+<p style="margin-bottom: 0cm;">To include the system wide CDE integration 
+ in your package, you should call the <b>&lt;path-to-staroffice-root&gt;/share/cde 
+ /dtappintegrate</b> script with the parameters <b>&lt;path-to-staroffice-root&gt; 
+  StarOffice 6.0 en</b> from the post-installation section of your package. 
+ Note: when you install StarOffice in a different language than english, you
+ will have to replace "en" with the ISO language code of the language you
+install for ( e.g. "de" for german ).&nbsp;</p>
+     
+<p style="margin-bottom: 0cm;">For proper deinstallation, you should invoke 
+ <b>/usr/dt/bin/dtappintegrate</b> with the parameters <b>-u -s &lt;path-to-staroffice-root&gt;</b>
+    and <b>rm -rf &lt;path-to-staroffice-root&gt;/dt </b>from the pre-deinstallation 
+ section of your package.<br>
+   <br>
+         </p>
+                 
+<p style="margin-bottom: 0cm;"><font size="4">D. GNOME 1.4 integration</font></p>
+                            
+<p style="margin-bottom: 0cm;"><font size="3">The GNOME 1.4 integration of 
+ </font>StarOffice<small><sup>TM</sup></small><font size="3"> consists of 
+a set of zip files containing the menu integration files and a small binary 
+ that does the user space filetype registration. As you may want the GNOME 
+ integration to be system wide, you can only take the corresponding files 
+as templates, but have to provide your own set of files.</font></p>
+     
+<p style="margin-bottom: 0cm;"><font size="3">To find the files provided by
+</font>StarOffice<small><sup>TM</sup></small><font size="3"> go back to your
+installation set and lookup the following strings in the <b>setup.ins</b>
+    file: group_pngs.zip, writer_pngs.zip, calc_pngs.zip, draw_pngs.zip,
+impress_pngs.zip  for the icons and gnomeappgroup.zip, gnomeappwriter.zip,
+gnomeappcalc.zip,  gnomeappdraw.zip, gnomeappimpress.zip for the .desktop
+templates. The "PackedName"  you will find close to the names stated above
+is the name of the f_xxxx zip  file archieve that includes the content of
+the original zip files. You can  either rename the files (e.g. f_0531 -&gt;
+&nbsp;</font><font size="3">group_pngs.zip)  or try to unzip the f_xxxx files
+directly.</font></p>
+     
+<p style="margin-bottom: 0cm;"><font size="3">If you want to register </font>
+  the StarOffice<small><sup>TM</sup></small><font size="3"> file types, you
+ may will find a list of them <a href="http://framework.openoffice.org/documentation/mimetypes/mimetypes.html">
+  here</a>.&nbsp; Note that there is currently a problem with Nautilus 1.x
+ with the XML file formats: Nautilus recognizes them as zip files (which
+is  correct), but does not offer a way to override this detection result
+for specific extensions.</font></p>
+      
+<p style="margin-bottom: 0cm;">      </p>
+                 
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+  E. GNOME 2 integration</font></p>
+    
+<p style="margin-bottom: 0cm;"><font size="3">In the upcoming 2.0 release
+ </font>GNOME will probably switch to UTF-8 encoding for the NLS strings
+in  the .desktop file, so you may use the KDE integration files as templates.<br>
+  </p>
+     
+<p style="margin-bottom: 0cm;"><font size="4"><br>
+  F. KDE integration<br>
+  </font><font size="3"><br>
+  The KDE 2.x integration of StarOffice<small><sup>TM</sup></small> consists
+ of two sets of zip files containing the menu integration files and the mime
+ registration files. These files contain a bunch of placeholders you will
+have to replace before using them. You may also think about changing the menu
+structure from being document based to be application based for the document
+based structure has the following drawbacks: One sees a document  (e.g. Textdocument)
+in the "Open with" list of the context menu of a</font>  StarOffice<small><sup>
+TM</sup></small> file and the application launch feedback also shows a document
+name instead of an application.</p>
+   
+<p style="margin-bottom: 0cm;"><font size="3">To find the files provided by
+</font>StarOffice<small><sup>TM</sup></small><font size="3"> go back to your
+installation set and lookup the following strings in the <b>setup.ins</b>
+     file: kdeappgroup.zip, kdeappwrite.zip, kdeappcalc.zip, kdeappdraw.zip,
+ kdeappimpress.zip for the menu .desktop templates and kdeappgroup.zip, kdeappwriter.zip, 
+kdeappcalc.zip, kdeappdraw.zip, kdeappimpress.zip for the icons and the file 
+type registration files. The "PackedName" you will find close to the names 
+stated above is the name of the f_xxxx zip file archieve that includes the 
+content of the original zip files.  You can either rename the files (e.g. 
+f_0546 -&gt; kdeappgroup.zip) or try to unzip the f_xxxx files directly.</font></p>
+   
+<p style="margin-bottom: 0cm;"><br>
+  </p>
+     
+<p style="margin-bottom: 0cm;"><font size="4">G. Java setup</font></p>
+     
+<p style="margin-bottom: 0cm;">coming soon ..<br>
+   </p>
+                 
+<p style="margin-bottom: 0cm;"><br>
+         </p>
+                 
+<p style="margin-bottom: 0cm; text-decoration: none;"><br>
+         </p>
+                 
+</body>
+</html>

Propchange: incubator/ooo/ooo-site/trunk/content/installation/how_to_repackage_so.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/installation/how_to_scp_oo.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/how_to_scp_oo.html?rev=1175543&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/how_to_scp_oo.html (added)
+++ incubator/ooo/ooo-site/trunk/content/installation/how_to_scp_oo.html Sun Sep 25 19:40:34 2011
@@ -0,0 +1,576 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE></TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice/5.2 (Win32)">
+	<META NAME="AUTHOR" CONTENT="Oliver Bolte">
+	<META NAME="CREATED" CONTENT="20001218;17461754">
+	<META NAME="CHANGEDBY" CONTENT="Ingo Schmidt">
+	<META NAME="CHANGED" CONTENT="20010205;15392152">
+	<STYLE>
+	<!--
+		@page { margin: 2cm }
+	-->
+	</STYLE>
+</HEAD>
+<BODY>
+<P ALIGN=CENTER STYLE="margin-bottom: 0cm"><B><FONT SIZE=5>The
+scp-project in OpenOffice.org<BR></FONT></B><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; font-weight: medium"><FONT SIZE=4>Introduction:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><SPAN STYLE="font-weight: medium"><FONT SIZE=3>The
+scp project contains the script-particles (scp) for OpenOffice.org.
+This project</FONT></SPAN> produces *.inf (Win) and *.ins (Unx) files
+which are used to direct the setup and the production of installation
+sets with lzip.</P>
+<P STYLE="margin-bottom: 0cm">The scp project directs the whole
+installation process for the OpenOffice.org. Following components are
+supported: Directorys, files, configuration items (for *.xml files),
+registry items (for windows registry), profile items (entries for the
+ini-files), folders, default installation path, help texts for setup,
+cinema text, modules and basic scripts.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>A. How to put a new file
+in the installation set:</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">Add a Gid item (e.g. like
+	GID_FILE_LIB_SFX ) <BR>into the scp/inc/gid.inc file.</P>
+	<P STYLE="margin-bottom: 0cm"></P>
+	<LI><P STYLE="margin-bottom: 0cm">For which project and which
+	setup-module is the new file relevant?</P>
+	<P STYLE="margin-bottom: 0cm">Setup: scp/source/global/setupzip.scp
+	this is for files needed by the setup.</P>
+	<P STYLE="margin-bottom: 0cm">Office: scp/source/office/files.scp
+	</P>
+	<P STYLE="margin-bottom: 0cm">and so on for calc, chart , ...<BR><BR>
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">a ) Standard filenames like
+	sfx615mi.dll or libsfx615ss.so can be integrated into<BR>the
+	files.scp (for OfficeFAT) with the macros</P>
+	<P STYLE="margin-bottom: 0cm"><BR>STD_LIB_FILE( GID_FILE_LIB_SFX ,
+	sfx )<BR><BR>
+	</P>
+	<P STYLE="margin-bottom: 0cm">or, if the dll needs to be registered
+	in the applicat.rdb:<BR><BR>
+	</P>
+	<P STYLE="margin-bottom: 0cm">STD_UNO_LIB_FILE( GID_FILE_LIB_DLL ,
+	dll)</P>
+	<P STYLE="margin-bottom: 0cm"><BR>Resource files are added
+	with<BR>STD_RES_FILE( GID_FILE_RES_SFX , sfx )</P>
+	<P STYLE="margin-bottom: 0cm"></P>
+	<P STYLE="margin-bottom: 0cm">This macro STD_RES_FILE expands the
+	file name to sfx61501.res for english or sfx61549.res for german.</P>
+	<P STYLE="margin-bottom: 0cm"><BR>b) Filenames whithout SUPD (this
+	is the version number, for example the 615) can be realised by
+	using:</P>
+  <i>
+  <BR>File GID_FILE_LIB_EXAMPLE
+  <P STYLE="margin-bottom: 0cm">        BIN_FILE_BODY;</P>
+  <P STYLE="margin-bottom: 0cm">        Styles          = (PACKED);</P>
+  <P STYLE="margin-bottom: 0cm">        Dir             = GID_DIR_PROGRAM;</P>
+  <P STYLE="margin-bottom: 0cm">        #ifdef UNX</P>
+  <P STYLE="margin-bottom: 0cm">        Name            =
+  &quot;libexample.so&quot;;</P>
+  <P STYLE="margin-bottom: 0cm">        #else</P>
+  <P STYLE="margin-bottom: 0cm">        Name            =
+  &quot;example.dll&quot;;</P>
+  <P STYLE="margin-bottom: 0cm">        #endif</P>
+  <P STYLE="margin-bottom: 0cm">    End<BR><BR> </i>    or, if the dll
+  needs to be registered in the applicat.rdb:<BR><BR><i>
+  </P>
+  <P STYLE="margin-bottom: 0cm">File GID_FILE_LIB_EXAMPLE_UNO</P>
+  <P STYLE="margin-bottom: 0cm">        BIN_FILE_BODY;</P>
+  <P STYLE="margin-bottom: 0cm">        Styles          =
+  (PACKED,UNO_COMPONENT);</P>
+  <P STYLE="margin-bottom: 0cm">        RegistryID      =
+  GID_STARREGISTRY_APPLICAT_RDB;</P>
+  <P STYLE="margin-bottom: 0cm">        Dir             =
+  GID_DIR_PROGRAM;</P>
+  <P STYLE="margin-bottom: 0cm">        #ifdef UNX</P>
+  <P STYLE="margin-bottom: 0cm">        Name            =
+  &quot;libexample_uno.so&quot;;</P>
+  <P STYLE="margin-bottom: 0cm">        #else</P>
+  <P STYLE="margin-bottom: 0cm">        Name            =
+  &quot;example_uno.dll&quot;;</P>
+  <P STYLE="margin-bottom: 0cm">        #endif</P>
+  <P STYLE="margin-bottom: 0cm">    End <BR><BR><BR>
+  </P>
+  </i>
+  <P STYLE="margin-bottom: 0cm">  c) Archive files as they come from the
+  extras project or any other zip-compressed file<BR>   can be included
+  by using following construct:<BR><BR>
+  <i>   File GID_FILE_EXTRA_EXAMPLE</P>
+  <P STYLE="margin-bottom: 0cm">             Dir             =
+  GID_DIR_EXAMPLE;</P>
+  <P STYLE="margin-bottom: 0cm">         ARCHIVE_TXT_FILE_BODY;</P>
+  <P STYLE="margin-bottom: 0cm">         Name            = &quot;example.zip&quot;;</P>
+  <P STYLE="margin-bottom: 0cm">    End</P>
+  <P STYLE="margin-bottom: 0cm"><BR>
+  </P></i>
+  <P STYLE="margin-bottom: 0cm">  d) Archive files with countrycode
+  (e.g. 01, 03, 07, ..., 96)</P>
+  <P STYLE="margin-bottom: 0cm">    in the filename (extras project) can
+  be included by using following construct:<BR><BR><i>   File
+  GID_FILE_EXTRA_EXAMPLE</P>
+  <P STYLE="margin-bottom: 0cm">             Dir             =
+  GID_DIR_EXAMPLE;</P>
+  <P STYLE="margin-bottom: 0cm">         ARCHIVE_TXT_FILE_BODY;</P>
+  <P STYLE="margin-bottom: 0cm">         EXTRA_ALL_LANG(example);</P>
+  <P STYLE="margin-bottom: 0cm">    End</P></i>
+  <P STYLE="margin-bottom: 0cm">    <BR>    Please notice, that the macro
+  EXTRA_ALL_LANG(example) expands to</P>
+  <P STYLE="margin-bottom: 0cm"><BR>
+  </P>
+  <P STYLE="margin-bottom: 0cm">    Name (01)  = &quot;example01.zip&quot;;</P>
+  <P STYLE="margin-bottom: 0cm">    Name (03)  = &quot;example03.zip&quot;;</P>
+  <P STYLE="margin-bottom: 0cm">    Name (30)  = &quot;example30.zip&quot;;</P>
+  <P STYLE="margin-bottom: 0cm">          o</P>
+  <P STYLE="margin-bottom: 0cm">          o</P>
+  <P STYLE="margin-bottom: 0cm">    Name (96)  = &quot;example96.zip&quot;;</P>
+  <P STYLE="margin-bottom: 0cm"></P>
+  <LI><P STYLE="margin-bottom: 0cm">The new file has to be linked to a
+  setup-module. Default is the root-module, meaning that this file
+  will be installed always and cannot be deselected during setup. If
+  the file belongs for example to the Calc-project, add its Gid to the
+  files section of the module in the file
+  scp/source/calc/module_calc.scp.</P>
+  <P STYLE="margin-bottom: 0cm"></P>
+  <LI><P STYLE="margin-bottom: 0cm">Conclusion:</P>
+  <P STYLE="margin-bottom: 0cm">If a new standard file is added to the
+  OpenOffice.org, two scp-files have to be updated:</P>
+  <P STYLE="margin-bottom: 0cm">scp/inc/gid.inc   (for the addition of
+  the new GID)</P>
+  <P STYLE="margin-bottom: 0cm">scp/source/files.scp  (for the
+  description of the file)</P>
+  <P STYLE="margin-bottom: 0cm"></P>
+</OL>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>B. Configurationitems</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Configurationitems are used to add or
+change configuration entries in xml files.</P>
+<P STYLE="margin-bottom: 0cm">There are several important subentries
+like Path, Key, Value, Styles and ModuleID.</P>
+<P STYLE="margin-bottom: 0cm">A typical item looks like following
+example:</P>
+<P STYLE="margin-bottom: 0cm">
+</P><i>
+<P STYLE="margin-bottom: 0cm">ConfigurationItem
+GID_CONFIGURATIONITEM_EXAMPLE</P>
+<P STYLE="margin-bottom: 0cm">	ModuleID = GID_MODULE_SO_ROOT;</P>
+<P STYLE="margin-bottom: 0cm">	Path =
+&quot;org.openoffice.Office.ExampleFile/Filters/draw_SGV_StarDraw_20&quot;;</P>
+<P STYLE="margin-bottom: 0cm">	Key = &quot;UIName&quot;;</P>
+<P STYLE="margin-bottom: 0cm">	Value = &quot;SGV - StarDraw 2.0&quot;;</P>
+<P STYLE="margin-bottom: 0cm">	Styles = (CFG_STRING, CREATE);</P>
+<P STYLE="margin-bottom: 0cm">End</P></i>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Path:</P>
+<P STYLE="margin-bottom: 0cm">The first part of this entry declares
+the filename without extension in this example</P>
+<P STYLE="margin-bottom: 0cm">org.openoffice.Office.ExampleFile.xml
+is the target file. The following part of the entry describes the
+path in the xml file.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Key and Value:</P>
+<P STYLE="margin-bottom: 0cm">Contain the entries in the xml file.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Styles:</P>
+<P STYLE="margin-bottom: 0cm">Defines the type of value:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">CFG_STRING:	Value = &quot;A string&quot;</P>
+<P STYLE="margin-bottom: 0cm">CFG_STRINGLIST:  Value = a list of
+strings</P>
+<P STYLE="margin-bottom: 0cm">CFG_BOOLEAN: 	Value = &quot;TRUE&quot;
+or &quot;FALSE&quot;</P>
+<P STYLE="margin-bottom: 0cm">CFG_NUMERIC:	Value = 1031</P>
+<P STYLE="margin-bottom: 0cm">CFG_BINARY:	Value is binary.</P>
+<P STYLE="margin-bottom: 0cm">CREATE:		Creates  a new entry in the
+xml file. If this entry exsists in the xml file no 			action takes
+place.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>C. Profile and
+ProfileItems</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">This part of setup is localized in the
+profile.scp and profile_xxx.scp files (where &#132;xxx&#147; means
+for example &#132;calc&#147; for different setup-modules).</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Profile declares the name and directory
+of an ini file. The gid name is needed in the ProfileItem declaration
+as ProfileID parameter. The ProfileItems are the entries in the form
+&#132;Key = Value&#147; of the ini-files.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm">Profile GID_PROFILE__EXAMPLE_INI</P>
+<P STYLE="margin-bottom: 0cm">    ModuleID = GID_MODULE_EXAMPLE;</P>
+<P STYLE="margin-bottom: 0cm">    Name = &quot;example.ini&quot;;</P>
+<P STYLE="margin-bottom: 0cm">    Dir = GID_DIR_EXAMPLE;</P>
+<P STYLE="margin-bottom: 0cm">    Styles		 = (NETWORK);</P>
+<P STYLE="margin-bottom: 0cm">End</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P></i>
+<P STYLE="margin-bottom: 0cm">Styles:</P>
+<P STYLE="margin-bottom: 0cm">NETWORK :  <SPAN STYLE="font-weight: medium">Network
+installation</SPAN></P>
+<P STYLE="margin-bottom: 0cm">WORKSTATION : Workstation installation</P>
+<P STYLE="margin-bottom: 0cm">INSTALL_INFO :  Only necessary for the
+install.ini</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm"> ProfileItem GID_PROFILEITEM_EXAMPLE_INI_TEST</P>
+<P STYLE="margin-bottom: 0cm">    ProfileID = GID_PROFILE_EXAMPLE_INI;</P>
+<P STYLE="margin-bottom: 0cm">    ModuleID = GID_MODULE_EXAMPLE;</P>
+<P STYLE="margin-bottom: 0cm">    Order = 2;</P>
+<P STYLE="margin-bottom: 0cm">    Section  = &quot;Example&quot;;</P>
+<P STYLE="margin-bottom: 0cm">    Key = &quot;test&quot;;</P>
+<P STYLE="margin-bottom: 0cm">    Value = &quot;testValue&quot;;</P>
+<P STYLE="margin-bottom: 0cm">End</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P></i>
+<P STYLE="margin-bottom: 0cm">ProfileID : GID of the ini file defined
+by Profile</P>
+<P STYLE="margin-bottom: 0cm">ModuleID :   Setup-module GID</P>
+<P STYLE="margin-bottom: 0cm">Section :  Declaration of the sectioname</P>
+<P STYLE="margin-bottom: 0cm">Order :    Numerical order of the entry</P>
+<P STYLE="margin-bottom: 0cm">Key and Value : Contain the content of
+the ini-file entry</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Language dependent Value entries are in
+the correspondent lng files.</P>
+<P STYLE="margin-bottom: 0cm">Several macros are used to handle these
+entries (xx = 01,03,...,96):</P>
+<P STYLE="margin-bottom: 0cm">ALL_LANG_STR_SECTION(str) expands to
+Section(xx) = &quot;str-xx&quot;</P>
+<P STYLE="margin-bottom: 0cm">ALL_LANG_STR_KEY(str) expands to Key
+(xx) = &quot;str&quot;</P>
+<P STYLE="margin-bottom: 0cm">ALL_LANG_STR_VALUE_LNG(ID) expands to</P>
+<P STYLE="margin-bottom: 0cm">Value (01) = &quot;Value text 01&quot;;</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>	&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>	&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Value (96) = &quot;...&quot;;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>when the content of the
+lng file is</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">[STR_VALUE_ID]</P>
+<P STYLE="margin-bottom: 0cm">01 = &quot;Value text 01&quot;</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>	&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>	&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm">96 = &quot;...&quot;</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">You can use the macros as follows:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm">ProfileItem GID_PROFILEITEM_EXAMPLE_INI_TEST</P>
+<P STYLE="margin-bottom: 0cm">	ProfileID = GID_PROFILE_INSTALL_INI;</P>
+<P STYLE="margin-bottom: 0cm">	ModuleID = GID_MODULE_PRG_IMPRESS_BIN;</P>
+<P STYLE="margin-bottom: 0cm">	Order = 2;</P>
+<P STYLE="margin-bottom: 0cm">	ALL_LANG_STR_SECTION(simpress-Filters);</P>
+<P STYLE="margin-bottom: 0cm">	ALL_LANG_STR_KEY(&quot;StarImpress 4.0
+Vorlage&quot;);</P>
+<P STYLE="margin-bottom: 0cm">	ALL_LANG_STR_VALUE_LNG(TEMPLATE_STAR_IMPRESS40);</P>
+<P STYLE="margin-bottom: 0cm">End</P></i>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>D. Directories</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>This part of setup is
+localized in the dir.scp and dir_xxx.scp files (where again &#132;xxx&#147;
+means for example &#132;calc&#147; for different setup-modules).</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm">Directory GID_DIR_EXAMPLE</P>
+<P STYLE="margin-bottom: 0cm">	ParentID		= PD_PROGDIR;</P>
+<P STYLE="margin-bottom: 0cm">	DosName         = &quot;example&quot;;</P>
+<P STYLE="margin-bottom: 0cm">	Styles          = (WORKSTATION,
+DELETE_ONLY, CHECK_TIMESTAMP,CREATE);</P>
+<P STYLE="margin-bottom: 0cm">End</P></i>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Styles:</P>
+<P STYLE="margin-bottom: 0cm">WORKSTATION :   Create directory on client
+side (Network installation only)</P>
+<P STYLE="margin-bottom: 0cm">CREATE :     Create empty directory. If
+setup copies a file into a directory the 					directory will be
+created automatically.</P>
+<P STYLE="margin-bottom: 0cm">DELETE_ONLY :   Setup removes this
+directory during deinstallation
+</P>
+<P STYLE="margin-bottom: 0cm">CHECK_TIMESTAMP : Will be only deleted
+when 'delete all' flag during deinstallation<BR>				was set. Usage
+with DELETE_ONLY flag only.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">PD_PROGDIR is predefined as the
+installation path.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=4>E. Modules</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>This part of setup is
+localized in the module.scp and module_xxx.scp files (and again &#132;xxx&#147;
+means for example &#132;calc&#147; for different setup-modules).</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Modules are used to
+declare installation components which are composited from files,
+directorys, basic procedures, profileitems, configurationitems. They
+are usally selectable or deselectable in the setup dialog box for
+custom installation.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Module GID_MODULE_EXAMPLE</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Name           =
+&quot;Example name&quot;;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Description  =
+&quot;Example description&quot;;       </FONT>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        ParentID =
+GID_MODULE_PARENT;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Files =
+(GID_FILE_EXAMPLE1,GID_FILE_EXAMPLE2);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Procedures   =
+(GID_PROCEDURE_EXAMPLE);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Minimal = YES;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Default   = YES;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Styles =
+(HIDDEN_ROOT);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>End</FONT></P></i>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Name: Name of the module.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Description: Description
+of the module.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Minimal: If set to YES,
+this component is part of a minimal installation.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Default:   If set to YES,
+this component is part of a standard installation.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Styles:	HIDDEN_ROOT: Hide
+the module in the dialog box for custom installation.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>	DONT_SELECT_BY_USER: The
+user can't change the selection status of the module.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3><U>Important:</U></FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>To
+switch Profiles, ProfileItems and ConfigurationItems with modules,
+the gid of the module is specified in the
+Profile/ProfileItem/ConfigurationItem ModuleID parameter.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><SPAN STYLE="text-decoration: none"><FONT SIZE=3>To
+switch customs, procedures, files and directories</FONT></SPAN>, the
+gid of these items are specified in</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>the similar Files,Customs,
+Dirs, Procedures parameters of the Module declaration.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>MOD_NAME_DESC(id):</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>The macro  MOD_NAME_DESC
+is very usefull, because of the language dependencies of the name and
+description entries. It is using the corresponding module.lng and
+module_xxx.lng files which contain the language dependent strings.</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Usage:  </FONT>
+</P><i>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>Module GID_MODULE_EXAMPLE</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>
+MOD_NAME_DESC(MODULE_EXAMPLE);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        ParentID =
+GID_MODULE_OPTIONAL;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Files =
+(GID_FILE_ZIP_ADDIN,GID_FILE_LIB_ROT,GID_FILE_LIB_DFA);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Procedures   =
+(GID_PROCEDURE_EXAMPLE);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Minimal = YES;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Default   = YES;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>        Styles =
+(HIDDEN_ROOT);</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>End</FONT></P></i>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>In this example the id
+MODULE_EXAMPLE expands to the appropriate</FONT> sections<BR>in the
+lng file:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>[STR_NAME_ MODULE_EXAMPLE]</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>01 = &quot;Example&quot;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>	&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>	&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>96 = &quot;....&quot;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>[STR_DESC_ MODULE_EXAMPLE]</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>01 = &quot;Example
+description&quot;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>	&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>	&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>96 = &quot;....&quot;</FONT></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3>The country codes have the
+following meaning:</FONT></P><BR>
+01: English<BR>
+03: Portuguese<BR>
+07: Russian<BR>
+30: Greek<BR>
+31: Dutch<BR>
+33: French<BR>
+34: Spanish<BR>
+39: Italian<BR>
+45: Danish<BR>
+46: Swedish<BR>
+48: Polish<BR>
+49: German<BR>
+55: Spanish (Brasil)<BR>
+81: Japanese<BR>
+82: Korean<BR>
+86: Chinese (simple)<BR>
+88: Chinese (traditional)<BR>
+90: Turkish<BR>
+96: Arabian<BR>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=4>F.
+Procedures</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><SPAN STYLE="text-decoration: none"><FONT SIZE=3>This
+part of setup is localized in the basic.scp and basic_xxx.scp files
+for Windows.</FONT></SPAN></P>
+<P STYLE="margin-bottom: 0cm">For UNIX the appropriate files are
+unxbasic.scp and unxbasic_xxx.scp <FONT SIZE=3> (and of course &#132;xxx&#147;
+means for example &#132;calc&#147; for different setup-modules).</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P><i>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>Procedure
+gid_Procedure_Example</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>	ProcName	=
+&quot;ExampleProcedure&quot;;</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>
+	Styles       	= (STANDALONE, WORKSTATION, INSTALL, BEFORE_INST);</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>	Code		=
+{Sub  ExampleProcedure</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>					&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>					&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>				Basic
+program</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>					&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>					&deg;</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>				End
+Sub</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>
+    };</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>End</FONT></P></i>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>Styles:	STANDALONE			Execute
+during standalone installation/deinstallation</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>  NETWORK :     Execute
+during network installation/deinstallation</FONT></P>
+<P STYLE="margin-bottom: 0cm"><SPAN STYLE="text-decoration: none"><FONT SIZE=3> WORKSTATION :  Execute
+during workstation installation/deinstallation</FONT></SPAN></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>  INSTALL :    Execute
+during installation</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>  UNINSTALL :   Execute
+during deinstallation</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>  BEFORE_INST :  Execute
+before creating directories/files.</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>  AFTER_INST :  Execute
+at the end of installation.</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>  PRE_SELECT_MODULE :  Execute
+before custom select dialog</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>						Only
+for one procedure allowed.</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>  LANGUAGE_SELECT_MODULE :
+Only important for checking the setup module selection</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm"><FONT SIZE=3><U>Important:</U></FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>The
+value of ProcName must be the name of the subroutine given in the
+first line of  the code parameter. In this example:
+'ExampleProcedure'.</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>The
+procedure GID must be added to a module by using the Procedures
+parameter in the module declaration (look above).</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; font-weight: medium; text-decoration: none">
+<FONT SIZE=4>G. Setup specifications</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Some setup-variables are available,
+which are replaced by the scp-linker or the setup itself.</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Linker-Variables:</P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">%PRODUCTNAME		w<SPAN STYLE="font-weight: medium">ill
+be substituted by the name of the product, here &#132;OpenOffice.org&#147;</SPAN></P>
+<P STYLE="margin-bottom: 0cm">%PRODUCTVERSION	w<SPAN STYLE="font-weight: medium">ill
+be substituted by the version of the product, here &#132;6.0&#147;</SPAN></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm">Setup-Variables:</P>
+<P STYLE="margin-bottom: 0cm">&lt;workpath&gt;, <SPAN STYLE="text-decoration: none"><FONT SIZE=3>&lt;progpath&gt;
+</FONT></SPAN> : Office-installation path</P>
+<P STYLE="margin-bottom: 0cm">&lt;productkey&gt; : only for the
+sversion-ini</P>
+<P STYLE="margin-bottom: 0cm"><SPAN STYLE="text-decoration: none"><FONT SIZE=3>Userdata:
+&lt;title&gt;, &lt;email&gt;, &lt;customernr&gt;, &lt;position&gt;</FONT></SPAN>,
+<SPAN STYLE="text-decoration: none"><FONT SIZE=3>&lt;city&gt;, &lt;fax&gt;,
+&lt;telefonwork&gt;</FONT></SPAN>, <SPAN STYLE="text-decoration: none"><FONT SIZE=3>&lt;telefonhome&gt;,
+&lt;street&gt;, &lt;company&gt;, &lt;country&gt;, &lt;state&gt;,
+&lt;zip&gt;, &lt;userfirstname&gt;</FONT></SPAN>, <SPAN STYLE="text-decoration: none"><FONT SIZE=3>&lt;username&gt;,
+&lt;userid&gt;, &lt;sequence_languages&gt;</FONT></SPAN></P>
+<P STYLE="margin-bottom: 0cm"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>The
+following preprocessor directive is available for OpenOffice.org:
+OSL_PRODUCT</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>Tip:
+If you make changes in one of the scp-files, please use the SUPD, for
+example if you include a new file in the files.scp use:</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>#if
+SUPD &gt; 622</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>...
+Here is the file-definition</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><FONT SIZE=3>#endif</FONT></P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+<P STYLE="margin-bottom: 0cm; text-decoration: none"><BR>
+</P>
+</BODY>
+</HTML>

Propchange: incubator/ooo/ooo-site/trunk/content/installation/how_to_scp_oo.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message