incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1206376 [2/2] - /incubator/ooo/ooo-site/trunk/content/installation/pics/
Date Fri, 25 Nov 2011 23:39:54 GMT
Added: incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_patch_flag.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_patch_flag.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_patch_flag.html
(added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_patch_flag.html
Fri Nov 25 23:39:52 2011
@@ -0,0 +1,113 @@
+<!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;16330200">
+</HEAD>
+<BODY LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT
SIZE=6>Understanding the PATCH flag</FONT></FONT></P>
+<P><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">
+The flat PATCH has to be used, if a file shall be included into a patch product. The flag
can be assigned 
+at the moment to scp items "File" and "RegistryItem". So the patch can add or exchange files
and write entries
+into the Windows Registry. The PATCH flag has to be assigned to every file, that was changed
after the final release
+of a product, if this file shall be included into a following patch for this final release.
+</P>
+<P>
+In the most simple case, you can just assign the PATCH flag directly in the scp project to
a file. Example:
+<BR><BR>
+<FONT FACE="Verdana, sans-serif">
+File gid_File_Bin_Open_Url<BR>
+    BIN_FILE_BODY;<BR>
+    Dir = gid_Dir_Program;<BR>
+    Name = "open-url";<BR>
+    Styles = (PACKED,PATCH);<BR>
+End<BR>
+</FONT>
+<BR>
+or to a RegistryItem:<BR><BR>
+<FONT FACE="Verdana, sans-serif">
+RegistryItem gid_Regitem_Software_Manufacturer_Productname_Productversion_Productcode_Install<BR>
+	ParentID = PREDEFINED_HKEY_LOCAL_MACHINE;<BR>
+	Subkey = "Software\%MANUFACTURER\%PRODUCTNAME%PRODUCTADDON\%PRODUCTVERSION\%PRODUCTCODE";<BR>
+	ModuleID = gid_Module_Root;<BR>
+	Name = "INSTALLLOCATION";<BR>
+	Value = "<progpath>";<BR>
+	Styles = (PATCH);<BR>
+End<BR>
+</FONT>
+</P>
+<P>
+If the file is defined in a macro, there is a "PATCH"-macro available:<br><br>
+STD_RES_FILE( gid_File_Res_Abp, abp)  # <- Not in Patch<br><br>
+STD_RES_FILE_PATCH( gid_File_Res_Abp, abp)  # <- In Patch<br><br>
+The following macros are available, that already contain the PATCH flag:<br><br>
+<FONT FACE="Verdana, sans-serif">
+PACKED_TXT_FILE_BODY_PATCH<br>
+ARCHIVE_TXT_FILE_BODY_PATCH<br>
+ARCHIVE_SUBST_FILE_BODY_PATCH<br>
+PACKED_LIB_FILE_BODY_PATCH<br>
+PACKED_FILTER_FILE_BODY_PATCH<br>
+STD_LIB_FILE_PATCH<br>
+STD_RES_FILE_PATCH<br>
+STD_FILTER_FILE_PATCH<br>
+STD_JAR_FILE_PATCH<br>
+UNO_JAR_FILE_PATCH<br>
+PACKED_UNO_LIB_FILE_BODY_PATCH<br>
+STD_UNO_LIB_FILE_PATCH<br>
+SPECIAL_UNO_LIB_FILE_PATCH<br>
+SPECIAL_UNO_COMPONENT_LIB_FILE_PATCH<br><br>
+</FONT>
+</P>
+<P>
+A little bit more complicated is the case, if only a selection of files shall be integrated
into a patch. This is
+relevant for all files, that are defined in scp project with style ARCHIVE. Such files can
contain hundreds of files, from
+which only a very small number shall be integrated into the patch. Therefore this file has
to get the flag PATCH and
+additionally a "Patchfiles" section, in which all files are listed in a comma separated list,
that shall be included into 
+the patch. Example:<br><br>
+<FONT FACE="Verdana, sans-serif">
+File gid_File_Share_Config_Sofficecfg_uiconfig_Zip<br>
+    TXT_FILE_BODY;<br> 
+    Styles = (ARCHIVE,PATCH);<br> 
+    Dir = gid_Dir_Share_Config_Sofficecfg;<br> 
+    Name = "uiconfig.zip";<br> 
+    Patchfiles = ("modules/dbbrowser/menubar/menubar.xml",<br> 
+                  "modules/scalc/menubar/menubar.xml",<br> 
+                  "modules/sglobal/accelerator/de/default.xml",<br> 
+                  "modules/sglobal/accelerator/en-GB/default.xml",<br> 
+                  "modules/sglobal/accelerator/en-US/default.xml",<br> 
+                  "modules/sglobal/accelerator/es/default.xml",<br> 
+                  "modules/sglobal/accelerator/fr/default.xml",<br> 
+                  "modules/sweb/accelerator/de/default.xml",<br> 
+                  "modules/sweb/accelerator/en-GB/default.xml",<br> 
+                  "modules/sweb/accelerator/en-US/default.xml",<br> 
+                  "modules/sweb/accelerator/es/default.xml",<br> 
+                  "modules/sweb/accelerator/fr/default.xml",<br> 
+                  "modules/swriter/accelerator/de/default.xml",<br> 
+                  "modules/swriter/accelerator/en-GB/default.xml",<br> 
+                  "modules/swriter/accelerator/en-US/default.xml",<br> 
+                  "modules/swriter/accelerator/es/default.xml",<br> 
+                  "modules/swriter/accelerator/fr/default.xml",<br> 
+                  "modules/simpress/accelerator/de/default.xml",<br> 
+                  "modules/simpress/accelerator/en-GB/default.xml",<br> 
+                  "modules/simpress/accelerator/en-US/default.xml",<br> 
+                  "modules/simpress/accelerator/es/default.xml",<br> 
+                  "modules/simpress/accelerator/fr/default.xml",<br> 
+                  "modules/simpress/menubar/menubar.xml",<br> 
+                  "modules/sdraw/accelerator/de/default.xml",<br> 
+                  "modules/sdraw/accelerator/en-gb/default.xml",<br>
+                  "modules/sdraw/accelerator/en-us/default.xml",<br> 
+                  "modules/sdraw/accelerator/es/default.xml",<br> 
+                  "modules/sdraw/accelerator/fr/default.xml",<br> 
+                  "modules/sdraw/menubar/menubar.xml");<br> 
+End
+</FONT">
+<br> 
+</P>
+</BODY>
+</HTML>

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

Propchange: incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_patch_flag.html
------------------------------------------------------------------------------
    svn:executable = *

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scipt_elements.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scipt_elements.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scipt_elements.html
(added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scipt_elements.html
Fri Nov 25 23:39:52 2011
@@ -0,0 +1,125 @@
+<!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;16330200">
+</HEAD>
+<BODY LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT
SIZE=6>Understanding
+the script elements</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The setup scripts is readable
+with a text editor. It contains blocks for different items, which can
+be read by the setup. If you open a setup script file, like setup.inf
+or setup.ins, you find blocks like</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">File
+gid_File_Lib_Db31<BR>Name = &quot;libdb32.dll&quot;;<BR>PackedName =
+&quot;f_0320&quot;;<BR>Size = 430080;<BR>Dir =
+gid_Dir_Program;<BR>Carrier = gid_DataCarrier;<BR>UnixRights =
+755;<BR>Date = &quot;23012002&quot;;<BR>Time = &quot;0600&quot;;<BR>Styles
+= (PACKED);<BR>End</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Each block begins with a special
+keyword and ends with an &bdquo;End&ldquo;. In this case the keyword
+is &bdquo;File&ldquo;, showing that the following definition block
+describes a file. As already shown in the document <A HREF="understanding_the_scipt_language.html">Understanding
+the script language</A> the block definition contains the name of the
+file, the packed name in the installation set, the size of the
+unpacked file, the directory in which the file shall be installed,
+the data carrier, the unix rights, the installation date and time and
+some special styles. Each definition block has to have a unique name,
+this is the so called global ID, GID. In the example above, the
+defintion block is named gid_File_Lib_Db31 </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">There are keywords for many
+actions the setup can make. Each keyword shows the beginning of a
+definition block. An installation set only contains definition
+blocks. You can define the following items:</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_file.html">File</A>:
+Describing a file in the installation set </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_directory.html">Directory</A>:
+Describes a directory the setup has to create </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_profile.html">Profile</A>:
+Describing an ini- or rc-file, the setup creates and fills during
+setup </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_profileitem.html">ProfileItem</A>:
+One line in the form Key = Value in a Profile, written by the setup</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_registryitem.html">RegistryItem</A>:
+One line in the form Key = Value in the setup registry, written by
+the setup  </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_folder.html">Folder</A>:
+Creates a directory in the Windows system, for example in the start
+menu directory</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_folderitem.html">FolderItem</A>:
+Creates the links to files in the created folder, for example in the
+start menu folder </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_shortcut.html">Shortcut</A>:
+Defines a link, which has to be created by the setup </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_unixlink.html">Unixlink</A>:
+Definition of a link in a Unix system, created by the setup</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_windowscustomaction.html">WindowsCustomAction</A>:
+A custom action that is executed by the Windows Installer service</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_mergemodule.html">MergeModule</A>:
+A merge module defines a Microsoft Merge Module, that is merged into the msi database during
+packaging process</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_module.html">Module</A>:
+Defines modules, which can be selected or deselected in a user
+defined installation. This item is also used to structure the setup
+script and all scp projects. A module contains lists of Files, Dirs,
+... etc. Each product can be defined as a group of modules. There is a special
+process for modules with language specific files: 
+<A HREF="scpitem_templatemodule.html">Language Specific Module</A>.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_installation.html">Installation</A>:
+This is the start definition in each setup script. It contains some
+global settings</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><A HREF="scpitem_scpaction.html">ScpAction</A>:
+This will not appear in the setup script in an installation set. It
+is only important for the packing process.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">There are two groups of items.
+The one group describes GIDs, which have to be connected to modules.
+The other group describes global definitions. As you can see, the
+modules have a special position in the setup script.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">A module looks like:</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif"><FONT FACE="Verdana,
sans-serif">Module
+gid_Module_Prg_Math_Bin<BR>MOD_NAME_DESC ( MODULE_PRG_MATH_BIN
+);<BR>ParentID = gid_Module_Prg_Math;<BR>Default = YES;<BR>Minimal =
+YES;<BR>Files =
+(gid_File_Dtd_Math,gid_File_Exe_Smath,gid_File_Html_W3c_Ipr,gid_File_Lib_Sm,gid_File_Res_Sm);<BR>Unixlinks=(gid_Unixlink_Mylink);<BR>Dirs
+= (gid_Dir_Mydir);</FONT><BR>End</FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><U>Module dependent items:</U></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">This module block defines the
+module gid_Module_Prg_Math_Bin, which describes the math module, that
+can be selected or deselected in a userdefined installation. As you
+can see, the module definition, contains lists of other GIDs. The
+lists <B>Dirs</B> (item <B>Directory</B>), <B>Files</B>
(item: <B>File</B>),
+<B>Unixlinks</B> (item: <B>Unixlink</B>), contain all GIDs, which
+describe definitions, that are installed by the setup, if the module
+is selected. Other items, like Profiles, ConfigurationItems, etc. are
+not assigned to a module, but have to contain the ModuleID in their
+definition!</FONT></P>
+<P><FONT FACE="Verdana, sans-serif"><U>Items without module
+assignment:</U></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">The items <B>Installation </B><SPAN
STYLE="font-weight: medium">and</SPAN>
+<B>ScpAction</B> are <SPAN STYLE="text-decoration: none">global</SPAN>,
+they do not belong to a module. The item <B>WindowsCustomAction</B>
+knows the file, that contains the code of the custom action.
+Therefore this is assigned to a file, not to a module. The item
+<B>ShortCut</B> is assigned to a File or to another ShortCut.</FONT></P>
+<P><BR><BR>
+</P>
+<P><BR><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

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

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scipt_language.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scipt_language.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scipt_language.html
(added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scipt_language.html
Fri Nov 25 23:39:52 2011
@@ -0,0 +1,106 @@
+<!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="AUTHOR" CONTENT="Ingo Schmidt">
+	<META NAME="CREATED" CONTENT="20020419;13085671">
+	<META NAME="CHANGED" CONTENT="20040204;19025249">
+</HEAD>
+<BODY LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT
SIZE=6>Understanding
+the script language</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif">The setup scripts is a file you
+can read with a normal text editor. In an installation set it is
+placed next to setup. The script contains only blocks, beginning with
+a special keyword and ending with an &bdquo;End&ldquo;. </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">A typical block looks like: </FONT>
+</P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">File
+gid_File_Lib_Db31<BR>Name = &quot;libdb32.dll&quot;;<BR>PackedName =
+&quot;f_0320&quot;;<BR>Size = 430080;<BR>Dir =
+gid_Dir_Program;<BR>Carrier = gid_DataCarrier;<BR>UnixRights =
+755;<BR>Date = &quot;23012002&quot;;<BR>Time = &quot;0600&quot;;<BR>Styles
+= (PACKED);<BR>End</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">This
+block is the <B><I>definition</I></B> of the global ID
+gid_File_Lib_Db31. Due to the beginning word <B>File</B> it describes
+a file. What information is needed for a file definition? First of
+all we see the name libdb32.dll. This is the physical name of the
+file. This file is packed in the installation set in a file name
+f_0320. The size of the unpacked libdb32.dll is 430.080 bytes. It
+shall be installed into a directory with the global ID
+gid_Dir_Program. This gid has to be definded in this setup script
+before this file definition. The Carrier is the medium, on which this
+file is stored. This is important for example for multi discs
+installations. If we install this product on a Unix platform we can
+give the Unix rights 755 to it. The installation date will be the
+01/23/2002, the installation time is 0600. This file is packed into
+the file f_0320, therefore it has the Style Packed. </FONT>
+</P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">This
+block you can find in the setup script of an installation set. The
+original setup script is located in the bin directory of the output
+tree. It was created in one of the scp-projects. The block of this
+file looks in the original setup script:</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">File
+gid_File_Lib_Db31<BR>Name = &quot;libdb32.dll&quot;;<BR>Dir =
+gid_Dir_Program;<BR>Carrier = gid_Datacarrier;<BR>UnixRights =
+755;<BR>Date = &quot; 23012002 &quot;;<BR>Time = &quot;0600&quot;;<BR>Styles
+= (PACKED);<BR>End</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">As you
+can see, scpzip adds the lines for the PackedName and the Size to the
+file definition. These are data, you cannot know, when you define a
+new file. </FONT>
+</P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">But how
+looks the original file definition. As you have already read, the
+setup script in the output tree is already platform and product
+independent. It was created from scp files, which were checked,
+preprocessed, linked and edited in many ways. The original file
+definition in the scp projects is the following definition block:</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">File
+gid_File_Lib_Db31<BR>BIN_FILE_BODY;<BR>#ifdef UNX<BR>Name =
+&quot;libdb-3.2.so&quot;;<BR>#else<BR>Name =
+&quot;libdb32.dll&quot;;<BR>#endif<BR>Dir = gid_Dir_Program;<BR>Styles
+= (PACKED);<BR>End</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">Obviously
+the name of this file is platform dependent. You can also see a macro
+name BIN_FILE_BODY. This is defined in the file macros.inc scp2
+project.</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">#define
+BIN_FILE_BODY FILE_BODY \<BR>UnixRights = 755</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">BIN_FILE_BODY
+contains only two lines: The macro FILE_BODY and the UnixRights.</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">In this
+way one file is defined. If you do not want, that the file belongs to
+the root module and is installed always, you have to assign the file
+to a module. Modules can be deselected by a user in a user defined
+installation process. By the way, modules are also defined in such
+blocks, beginning with the keyword Module. These module definitions
+contain lists of files, of procedures and whatever can be defined in
+a setup script. One module is a root module, showing that it cannot
+be deselected during the setup.  If a module contains the lines:</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">Default
+= YES;<BR>Minimal = YES;</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">it is
+selected in a Default and Minimal installation. The directories in
+the scp projects represent the modules. The directory scp2/ooo
+contains all files, registryitems, ... that belong to the root
+module. In the directory scp2/cde you find all the content of the cde
+module.</FONT></P>
+<P STYLE="line-height: 100%"><FONT FACE="Verdana, sans-serif">A
+product like an OpenOffice.org can be understand as the addition of
+all of these modules. All the defined scp files in the scp2 directory
+are bound together by the linker par2script.pl, who gets his
+information from the product definition in scp2/util/makefile.mk.</FONT></P>
+<P STYLE="line-height: 100%"><BR><BR>
+</P>
+<P STYLE="line-height: 100%"><BR><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

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

Added: incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scp_project.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scp_project.html?rev=1206376&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scp_project.html
(added)
+++ incubator/ooo/ooo-site/trunk/content/installation/pics/understanding_the_scp_project.html
Fri Nov 25 23:39:52 2011
@@ -0,0 +1,118 @@
+<!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;16142900">
+</HEAD>
+<BODY LANG="de-DE" DIR="LTR">
+<P ALIGN=LEFT STYLE="font-weight: medium"><FONT FACE="Verdana, sans-serif"><FONT
SIZE=6>Understanding
+the scp2 project</FONT></FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>What are scp files?</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">scp is the abbreviation for
+<B>script particle</B>. Every scp file is a small part of the <B>setup
+script</B>, which can be found in the installation set next to the
+setup. The setup script contains the information about the
+installation of OpenOffice.org. Every script particle contains a
+little information, for example about the kde integration, or the
+readme files or entries for the Windows registry. You will see, there
+are many, many different scp files for many different applications.</FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>When do I have to make changes
+in the scp2 project?</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Changes in the scp2 project are
+necessary, if the installation of OpenOffice.org has to be changed.
+This can include a new file, or an additional entry into the windows
+registry. Anything that is done by the setup, has to be available in
+the setup script. Every file and every entry into the Windows
+registry is written in the setup script in this special setup script
+language. In detail the setup script can contain the following
+information: </FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><I><B>Setup Modules</B></I>,
+<I><B>Files</B></I>, <I><B>Directories</B></I>,
<I><B>Profiles</B></I>
+(ini-files), <I><B>ProfileItems</B></I> (entries into ini-files),
+<I><B>RegistryItems</B></I> (entries into the Windows registry),
+<I><B>Folder</B></I> and <I><B>FolderItems</B></I>
(Directories and
+Links in the Windows system directories), <I><B>ShortCuts</B></I>
+(Links to defined files or other Shortcuts), <I><B>UnixLinks</B></I>
+(Links to any location in the system), <I><B>WindowsCustomActions</B></I>
+(Windows Installer specific actions), <I><B>ScpActions</B></I>
+(copying files from the output tree into the installation set (only
+for the ZipDirector and lzip)) and <I><B>Installation</B></I> (for
+global installation parameters). </FONT>
+</P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>How do we build the setup
+script?</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">The setup script is made of the
+script particle. These particle contain information about the
+languages, the platform, the different products etc. Therefore the
+scp files are first of all edited by a preprocessor, who gets the
+necessary parameter. Then the program pre2par.pl prepares the files
+for the linker par2script.pl. The results of pre2par.pl are par-files
+(same filename, but extension .par), which you can find in the output
+tree in the par directory.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Which par files for which
+products and which platforms have to be built, is determined in the
+makefile.mk in the local source directories of the different scp
+projects. After creating the par files, the linker links all
+necessary par files to the different setup scripts. Which par files
+are needed for which platform and which product is described in the
+makefile.mk in the util directory of the different scp projects.</FONT></P>
+<P><FONT FACE="Verdana, sans-serif">The resulting setup script still
+contains all information for the different languages we support, but
+is specified for one product and one platform. Therefore in the last
+step of creating installation sets the scpzip packs all files which
+are mentioned in the setup script, writes this information into the
+script and changes the script corresponding to the desired language. </FONT>
+</P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>Which scp projects exist?</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">Currently the project containing
+scp files is named <B>scp2</B>.</FONT></P>
+<P><BR><BR>
+</P>
+<P><FONT FACE="Verdana, sans-serif"><B>Last changes in the scp
+structure</B></FONT></P>
+<P><FONT FACE="Verdana, sans-serif">
+Caused by the strict separation of language dependent files and language
+independent files and by the increased number of supported languages for
+OpenOffice.org, a new mechanism was required, to generate modules with language
+specific files automatically. In this context a new concept with sct-files
+and modules with flag TEMPLATEMODULE was introduced into src680m242.
+sct is the abbreviation for script template files.
+</FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">
+During the scp build process, Perl programs expand the content of the sct files
+to content that would normally be defined in scp files. But the Perl programs
+"know" the supported languages and are therefore able to create a huge number
+of scp modules automatically.
+</FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif">
+The assignment of "Files", "Dirs" or other items can be achieved by using 
+template modules, that are not used to define "real" modules, but only
+assignments to modules. This template modules require the flag 
+TEMPLATEMODULE. This modules can be included from every non template
+module using the key "Assigns=...". Please find more information
+<A HREF="scpitem_templatemodule.html">here</A>.
+</FONT>
+</P>
+<P><FONT FACE="Verdana, sans-serif"> </FONT>
+</P>
+<P><BR><BR>
+</P>
+<P><BR><BR>
+</P>
+</BODY>
+</HTML>
\ No newline at end of file

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



Mime
View raw message