[Lxr-commits] CVS: html/en bugsandlimits.shtml, 1.14, 1.15 index.shtml, 1.9, 1.10 newfeatures.shtml
Brought to you by:
ajlittoz
From: Andre-Littoz <ajl...@us...> - 2013-11-07 16:17:55
|
Update of /cvsroot/lxr/html/en In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv8718/en Modified Files: bugsandlimits.shtml index.shtml newfeatures.shtml troubleshooting.shtml Log Message: Fixes, new 2.0 features, new tip for '500 Internal Server Error' Index: bugsandlimits.shtml =================================================================== RCS file: /cvsroot/lxr/html/en/bugsandlimits.shtml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -d -r1.14 -r1.15 --- bugsandlimits.shtml 19 Apr 2013 12:23:55 -0000 1.14 +++ bugsandlimits.shtml 7 Nov 2013 16:17:52 -0000 1.15 @@ -20,6 +20,47 @@ </p> <h2>Known bugs</h2> <ul> + <li>Ubuntu + <ul> + <li>Apache web server + <p class="normal"> +A configuration file is dependent upon <em>mod_version</em> Apache module +but Ubuntu Apache (reported at least for Ubuntu 12.04 LTS) +does not load the module by default. +To enable it run the following command: + </p> +<pre class="shell"> +$ <kbd>sudo a2enmod version</kbd> +</pre> + <p class="normal"> +and restart the server. + </p> + </li> + <li>Templates not found (weird screen) + <p class="normal"> +When LXR scripts are launched, +the current working directory is not set to the <em>LXR root directory</em>. +OS-relative file paths in <em>lxr.conf</em> cannot be correctly resolved. + </p> + <p class="normal"> +To fix the problem, +edit <em>custom.d/lxr.conf</em>, "HTML subsection", +and add the OS-absolute path of the LXR root directory +in front of all HTML template designations. +When done, +copy the modified file to its final destination as usual. + </p> + <p class="comment caution"> +DO NOT CHANGE parameters <code>'stylesheet'</code> and +<code>'alternate_stylesheet'</code> +which are not file paths but HTML references. + </p> + <p class="comment"> +This bug may also be Apache specific. + </p> + </li> + </ul> + </li> <li>Release 1.1.0 <ul> <li class="normal"> Index: index.shtml =================================================================== RCS file: /cvsroot/lxr/html/en/index.shtml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -d -r1.9 -r1.10 --- index.shtml 26 Jan 2013 09:44:19 -0000 1.9 +++ index.shtml 7 Nov 2013 16:17:52 -0000 1.10 @@ -80,12 +80,13 @@ <p class="normal"> This is a step-by-step <em>How to install LXR</em> guide for the latest release. -Follow these links for previous releases: -<a href="0-11-InstallSteps/0-11-install.shtml">0.11</a>, -<a href="InstallSteps/install.shtml">0.9.x and 0.10.x</a>. -For older releases, -read <em>INSTALL</em> file that ships with the software. </p> + <ul>Follow these links for previous releases: + <li><a href="0-11-InstallSteps/0-11-install.shtml">0.11</a></li> + <li><a href="InstallSteps/install.shtml">0.9.x and 0.10.x</a></li> + <li>Older releases, +read <em>INSTALL</em> file that ships with the software</li> + </ul> </li> <li> <a href="advancedconfig.shtml"> @@ -141,53 +142,53 @@ Release numbering scheme </a> </li> - <li>Demo: the LXR tree cross-referenced by LXR itself - <p class="comment"> -Releases 0.9.8 to 1.1 can be displayed and compared. - </p> - <p class="comment"> + <li><a href="styles.shtml"> + Typographical conventions + </a> + of this site + </li> + <li><a href="logos.shtml"> + Candidate logos + </a> + </li> + </ul> + + <h2>Demo: the LXR tree cross-referenced by LXR itself</h2> + <p class="comment"> +Releases 0.9.8 to 1.2.0 can be displayed and compared. + </p> + <p class="comment"> This demo exhibits two tree-variants: - </p> - <ul> - <li> + </p> + <ul> + <li> <a href="/lxr/source/">"classical" plain files tree</a> containing several released versions - </li> - <li> + </li> + <li> <a href="/cvs/source">CVS repository tree</a> containing all development history - <p class="normal"> + <p class="normal"> Due to SourceForge restrictions, it is only a snapshot. The date when it was taken is shown as the path root. - </p> - </li> - </ul> - <p class="normal"> -Notes: </p> - <p class="comment"> + </li> + </ul> + <p class="normal"> +Notes: + </p> + <p class="comment"> Since SourceForge's Perl is 5.8.8, LXR engines 1.0 and higher cannot be used. You will not see the latest improvements and features. - </p> - <p class="comment"> + </p> + <p class="comment"> SourceForge has a complex configuration where some support tools are removed from web servers to improve security. Consequently, some LXR features do not work as expected (<em>e.g.</em> annotations in file display under CVS). - </p> - </li> - <li><a href="styles.shtml"> - Typographical conventions - </a> - of this site - </li> - <li><a href="logos.shtml"> - Candidate logos - </a> - </li> - </ul> + </p> <h2>Download and summary information</h2> <p class=normal> Index: newfeatures.shtml =================================================================== RCS file: /cvsroot/lxr/html/en/newfeatures.shtml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -d -r1.14 -r1.15 --- newfeatures.shtml 14 Mar 2013 18:21:53 -0000 1.14 +++ newfeatures.shtml 7 Nov 2013 16:17:52 -0000 1.15 @@ -15,6 +15,64 @@ <!--#set var="homePageHeader" value="0" --> <!--#include virtual="/backstore/header.shtml" --> <ul> + <li><strong>Release 2.0</strong> + <ul> + <li class="classics"><del><em>genxref</em> goes parallel</del> + <p class="normal"> +Careful optimisation of current code dwindles the interest of multi-thread technology. +Multi-thread code is more complex and needs sophisticated database table locking strategy. +Experiments have shown this added complexity brings little gain on big projects +and slightly longer indexing times on small projects. + </p> + <p class="normal"> +However, this work uncovered very subtle bugs, or rather inaccuracies, +in the parser. + </p> + <p class="comment"> +As a net result, <em>genxref</em> performance is now x1.5 over release 1.2.0. +Indexing times are shortened by 33%. + </p> + </li> + <li class="classics">Multiple-trees context + <p class="normal"> +Tree designation in URL moved into <code>PATH_INFO</code> instead of +<code>SERVER_NAME</code> or <code>SCRIPT_NAME</code>. + </p> + <p class="comment"> +This is a new possibility, you do not need to modify your present trees. +This designation variant offers simpler and more robust web server configuration. +Adding or removing a tree is consequently only a matter of editing +<em>lxr.conf</em> without reconfiguring the web server. + </p> + </li> + <li class="classics">Better HTTP initialisation + <p class="normal"> +Printing a message on screen under catastrophic events during +initialisation now possible, avoiding the disturbing "blank screen" situation. + </p> + </li> + <li class="classics">Better error handling + <p class="normal"> +<em>Browsing</em>: errors and warnings are also printed on screen, +reducing the necessity to read them from the server log files. + </p> + <p class="normal"> +<em>Configuration</em>: most user data is now checked against expected format +thus detecting early some trivial mistakes. + </p> + </li> + <li class="classics">Experimental support of +<strong>Nginx</strong>, <strong>Cherokee</strong> +and <strong>thttpd</strong> web servers + </li> + <li class="classics"><em>User's Manual</em> updated + </li> + <li class="classics"><em>Developer's Manual</em> available + </li> + <li class="classics">Bug fixes + </li> + </ul> + </li> <li><strong>Release 1.2</strong> <ul> <li class="classics">Generic parser include feature rearchitectured Index: troubleshooting.shtml =================================================================== RCS file: /cvsroot/lxr/html/en/troubleshooting.shtml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- troubleshooting.shtml 23 Sep 2012 16:48:10 -0000 1.4 +++ troubleshooting.shtml 7 Nov 2013 16:17:52 -0000 1.5 @@ -129,6 +129,17 @@ <em>lighttpd-lxrserver.conf</em>. </p> </li> + <li><code class="error"><strong>500 Internal Server Error</strong></code> + <p class="normal"> +<strong>Apache</strong> <em>.htaccess</em> file contains +2.4 directives while your server is level 2.2, +leading to directive rejection and server abort. + </p> + <p class="comment"> +This is usually caused by an erroneous answer during configuration. +See <a href="Tips/tiperror500.shtml">this tip</a> for a fix. + </p> + </li> <li><code class="error"><strong>The directory/file <em>xxx</em> does not exist</strong></code> <p class="normal"> If the directory or file does not exist in this version; @@ -193,6 +204,10 @@ </ul> <h2>Errors entered in web-server log</h2> + <p class="comment"> +Starting with release 2.0, +these errors are also displayed on screen. + </p> <ul> <li><code class="error"><strong>Warning: template <em>xxx</em> does not exist</strong></code> <p class="normal"> |