[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fink-commits
Subject:    web/xml/packaging packaging.en.xml,1.19,1.20
From:       Daniel Macks <dmacks () users ! sourceforge ! net>
Date:       2004-03-31 20:08:37
Message-ID: E1B8m0r-0006AB-3N () sc8-pr-cvs1 ! sourceforge ! net
[Download RAW message or body]

Update of /cvsroot/fink/web/xml/packaging
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23357

Modified Files:
	packaging.en.xml 
Log Message:
Improved description of SplitOff processing.
Noted that SplitOff(N) may be handled out-of-order in the future.


Index: packaging.en.xml
===================================================================
RCS file: /cvsroot/fink/web/xml/packaging/packaging.en.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -r1.19 -r1.20
--- packaging.en.xml	30 Mar 2004 09:46:19 -0000	1.19
+++ packaging.en.xml	31 Mar 2004 20:08:34 -0000	1.20
@@ -2291,15 +2291,15 @@
 multiple packages.  
 The install phase begins as usual, with the execution of the 
 <code>InstallScript</code> and <code>DocFiles</code> commands.
-A <code>SplitOff</code> field, if present, then triggers the
-creation of a
-second install directory.  Within the 
-<code>SplitOff</code> field, the new install directory is referred to as %i,
+A <code>SplitOff</code> or <code>SplitOff<em>N</em></code> field, if present, then \
triggers the +creation of an
+additional install directory.  Within the 
+<code>SplitOff</code> or <code>SplitOff<em>N</em></code> field, the new install \
directory is referred to as %i,  while the original install directory of the parent 
 package is referred to as %I.
 </p>
 <p>
-The <code>SplitOff</code> field must contain a number of fields of its
+Each <code>SplitOff</code> and <code>SplitOff<em>N</em></code> field must contain a \
number of fields of its  own.  In fact, it resembles a complete package description, \
but with  certain fields missing.  Here is what belongs in the sub-description
 (by category):
@@ -2308,32 +2308,45 @@
 <li>Initial Data: Only the <code>Package</code> needs to be specified,
 everything else is inherited from the parent package.  You may modify
 <code>Type</code> and <code>License</code> by declaring the field
-within the <code>SplitOff</code>.  Percent expansion can be used, and
+within the <code>SplitOff</code> or <code>SplitOff<em>N</em></code>.  Percent \
expansion can be used, and  it is often convenient to refer to the name %N of the \
parent  package.</li>
 <li>Dependencies: All of these are allowed.</li>
 <li>Unpack Phase, Patch Phase, Compile Phase: These fields are irrelevant
 and will be ignored.</li>
 <li>Install Phase, Build Phase: Any of these fields are allowed (except
-that <code>SplitOff</code> should not be used within a <code>SplitOff</code>
-field).</li>
+that SplitOffs cannot themselves contain additional SplitOffs).</li>
 <li>Additional Data: These are inherited from the parent package but may
-be modified by declaring the field within the <code>SplitOff</code>.</li>
+be modified by declaring the field within the <code>SplitOff</code> or \
<code>SplitOff<em>N</em></code>.</li>  </ul>
 <p>
 During the install phase, the <code>InstallScript</code> and 
 <code>DocFiles</code> of the parent package are executed first.
-Next comes the <code>Files</code> command specified in the
-<code>SplitOff</code> field, which causes the listed files and directories
+Next comes processing of the <code>SplitOff</code> and \
<code>SplitOff<em>N</em></code> fields. For each such field in turn, the \
<code>Files</code> command causes the listed files and directories  to be moved from \
the parent's installation directory %I to the  current installation directory %i.  \
                Then the <code>InstallScript</code>
-and <code>DocFiles</code> of the <code>SplitOff</code> package are
+and <code>DocFiles</code> of the given <code>SplitOff</code> or \
<code>SplitOff<em>N</em></code> package are  executed.  
 </p><p>
-If there are additional sub-packages specified with <code>SplitOff2</code>,
-<code>SplitOff3</code>, etc., this same sequence of commands
-(<code>Files</code>, <code>InstallScript</code>, <code>DocFiles</code>)
-is executed for each of them in turn.
+At this time, the <code>SplitOff</code> is processed first (if
+present), followed by each <code>SplitOff<em>N</em></code> in
+numerical order by N. However, this may change in the future, so, for
+example, instead of:
+</p>
+<codeblock>
+SplitOff: &lt;&lt;
+  Description: Some header files
+  Files: include/foo.h include/bar.h
+&lt;&lt;
+SplitOff2: &lt;&lt;
+  Description: All other header files
+  Files: include/*
+&lt;&lt;
+</codeblock>
+<p>
+which only works correctly if <code>SplitOff</code> is processed
+before <code>SplitOff2</code> it's safer to list explicitly the files
+for each (or use more specific filename globs).
 </p><p>
 During the build phase, the pre/post install/remove scripts for each of
 the packages is constructed by using the build phase commands which



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Fink-commits mailing list
Fink-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-commits


[prev in list] [next in list] [prev in thread] [next in thread]