Update of /cvsroot/lxr/html/prototype/LxrConf
In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv10005/prototype/LxrConf
Modified Files:
lxrconfexclude.shtml lxrconfmaps.shtml lxrconftreeparms.shtml
Log Message:
Update for 1.1 features
Index: lxrconfexclude.shtml
===================================================================
RCS file: /cvsroot/lxr/html/prototype/LxrConf/lxrconfexclude.shtml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- lxrconfexclude.shtml 3 Nov 2012 21:07:08 -0000 1.2
+++ lxrconfexclude.shtml 3 Jan 2013 11:07:04 -0000 1.3
@@ -51,6 +51,34 @@
, 'ignoredirs' => [ 'CVSROOT', '.git' ]
</pre>
</div>
+ <ul class="version">
+ <li class="classics">Release 1.1 and higher
+ <p class="normal">
+Should you need a finer-grained control on directory exclusion,
+parameter <code>'filterdirs'</code> operates on the full LXR path
+(rooted at <code>'virtroot'</code>):
+ </p>
+<pre class="example">
+, 'filterdirs' => [ <em>regular_expressions</em> ]
+</pre>
+ <p class="normal">
+By convention for this test,
+directory paths begin with a separator (<code>/</code>)
+and are <strong>NOT</strong> terminated by a separator.
+ </p>
+ <p class="normal">
+Regular expressions are used one after the other in the order
+in which they are specified
+until a match
+(in which case the directory is excluded).
+ </p>
+ <p class="normal caution">
+Usage of this parameter is strongly discouraged because of the
+processing time needed.
+Read the User's Manual for further explanation and examples.
+ </p>
+ </li>
+ </ul>
<h2><a name="excludeFiles">Files</a></h2>
<p class="normal">
@@ -116,4 +144,32 @@
</p>
</li>
</ul>
+ <ul class="version">
+ <li class="classics">Release 1.1 and higher
+ <p class="normal">
+Should you need a more precise screening rule,
+parameter <code>'filterfiles'</code> operates on the full LXR path
+(rooted at <code>'virtroot'</code>):
+ </p>
+<pre class="example">
+, 'filterfiles' => [ <em>regular_expressions</em> ]
+</pre>
+ <p class="normal">
+By convention for this test,
+file paths begin with a separator (<code>/</code>).
+ </p>
+ <p class="normal">
+Regular expressions are used one after the other in the order
+in which they are specified
+until a match
+(in which case the file is excluded).
+ </p>
+ <p class="normal caution">
+Usage of this parameter is also strongly discouraged because of the
+processing time needed.
+Read the User's Manual for further explanation and examples.
+ </p>
+ </li>
+ </ul>
+
<!--#include virtual="/backstore/footer.shtml" -->
Index: lxrconfmaps.shtml
===================================================================
RCS file: /cvsroot/lxr/html/prototype/LxrConf/lxrconfmaps.shtml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- lxrconfmaps.shtml 23 Sep 2012 16:48:10 -0000 1.4
+++ lxrconfmaps.shtml 3 Jan 2013 11:07:04 -0000 1.5
@@ -195,7 +195,8 @@
system of the open source world.
To cope with sub-architecture variants needs more variable definitions
and more <code>'incprefix'</code> and <code>'maps'</code> rules.
-Configuring LXR for the kernel deserves a full chapter.
+Configuring LXR for the kernel deserves a
+<a href="/<!--#echo var="langPrefix" -->Tips/tipkernel.shtml" title="Linux kernel include configuration">full chapter</a>.
</p>
</div>
</div>
Index: lxrconftreeparms.shtml
===================================================================
RCS file: /cvsroot/lxr/html/prototype/LxrConf/lxrconftreeparms.shtml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- lxrconftreeparms.shtml 3 Nov 2012 21:07:08 -0000 1.6
+++ lxrconftreeparms.shtml 3 Jan 2013 11:07:04 -0000 1.7
@@ -44,6 +44,9 @@
, 'sourceaccess' => <em>HTML_access_to_source_tree</em> # 0.10+
, 'ignoredirs' => [ <em>list_of_directories_to_ignore</em> ]
+, 'filterdirs' => [ <em>list_of_regexps_for_directories</em> ] # 1.1+
+, 'ignorefiles'=> <em>regexp</em> # 1.1+
+, 'filterfiles'=> [ <em>list_of_regexps_for_files</em> ] # 1.1+
, 'incprefix' => [ <em>list_of_include_directories</em> ]
, 'maps' => { <em>rules_for_path_transformation</em> } # -0.11 (see note below)
, 'maps' => [ <em>rules_for_path_transformation</em> ] # 1.0+
@@ -75,5 +78,32 @@
Perl-type of <code>'maps'</code> parameter changed in release 1.0 to allow
a controlled application order of the rules.
</p>
+ <p>Deprecation notes:</p>
+ <ul>
+ <li class="normal"><code>'baseurl'</code> and <code>'baseurl_aliases'</code>
+ <p class="normal">
+<code>'baseurl_aliases'</code> are error-prone
+because they require exact partial duplication from <code>'baseurl'</code>.
+Moreover, both require to copy <code>'virtroot'</code>.
+ </p>
+ <p>
+<code>'host_names'</code> and <code>'virtroot'</code> must be preferred
+because they separate the host names list from the virtual root,
+removing redundancies and possible typing errors.
+ </p>
+ </li>
+ <li class="normal"><code>'glimpsedir'</code> and <code>'swishdir'</code>
+ <p class="normal">
+If you define <code>'glimpsedirbase'</code> and/or <code>'swishdirbase'</code>
+in the global section,
+these tree-parameters are automatically generated as
+<em>value(</em><code>'glimpsedirbase'</code><em>)/value(</em><code>'virtroot'</code><em>)</em>.
+ </p>
+ <p class="normal">
+Of course, as usual, explicitly coding <code>'glimpsedir'</code>
+and/or <code>'swishdir'</code> in a tree section overrides the default automatic behaviour.
+ </p>
+ </li>
+ </ul>
<!--#include virtual="/backstore/footer.shtml" -->
|
