Bugs in Older and Obsolete LXR Releases

• genxref script for swish-e users

  A clumsy typo was left at line 240, which should read:

  $toolloc = `which swish-e 2>/dev/null`;

  i.e. remove the extraneous "h".

  This typo prevents detection of the swish-e engine when it has been installed in a "standard" location.

  A space is also missing at line 518, which should read:

  . " -f ".$config->swhishdir."/".$releaseid.".index" The -f is catenated to the directory name, giving a non-existent directory and leading to incorrect parsing of the rest of the arguments. The command then always fails and the search database is not initialised.
• New initial-config.sh script erroneously leaves templates/ directory with r--r--r-- permissions preventing any access to it. Fix permissions with $ chmod -R a+x templates/

  After any copy from templates/ directory, fix file permissions to allow write/update:

  $ cp templates/some_file lxrconf.d/ $ chmod u+w lxrconf.d/some_file Note: this is not a bug but a consequence of the "read-only" state of templates/ directory.
• In lxr.conf, parameter 'stylesheet' is defined as 'templates/html/lxr.css' instead of '/templates/lxr.css'.
• Under some Linux distributions, in single tree context (the most frequent case), Apache does not access the LXR root directory when it is different from the usual /var/www/. Remove the caret (^) in the Alias directive (line 28) of file templates/Apache/apache-lxrserver.conf to read: Alias /lxr "your_LXR_root_directory"

• Due to shameful haste and quality assurance breach, version 0.10 was released with an unforgivable bug. 0.10.1 corrected it but introduced another one. 0.10.2 partially corrected it, leaving a misplaced % character in a critical subroutine. Upgrade to latest release.
• Browsing include files

  If you change the value of any variable (i.e. version, architecture, …) after clicking on an include link, you may get a "file does not exist" error message because the rewrite rules are not correctly recomputed.

  Fixed in release 0.11

Prior to release 2.0.0, error messages are only sent to the browser error log. This usually requires administrator privileges to retrieve the information.

Starting with release 0.11, this directory is set to "read-only" mode to discourage people from making changes. It thus becomes a reliable reference for stored files. Any LXR customisation must be done in the custom.d/ directory (lxrconf.d/ prior to release 1.0).

• Only CVS is partially working

  In particular, import branches are not handled.

  Git Perl library being broken, trying to access a Git repository causes error termination.

• Free-text search

  Unavailable due to the specific format of the VCS database (read: they do not use plain files).

CVS does not manage version for directories. If you change version for something other than HEAD, you get the infamous "file does not exist" error message.