Your message dated Fri, 22 Dec 2006 17:49:13 +0100
with message-id <[EMAIL PROTECTED]>
and subject line lxr: README.gz is specific to linux
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: lxr
Version: 0.3.1-2
Severity: minor

README.Debian.gz is very useful for setting up lxr, but is most specific
to linux. I wish to use lxr with a different code base. I have followed
the instructions and attempted to substitute my codebase for linux where
appropriate to no avail. In particular, I find the following paragraph
difficult to understand:

        "Generate the identifier database.  Go to the
        /var/lib/lxr/source/, create a subdirectory (e.g. "2.4.6") and
        put the linux source in this subdirectory (the subdirectory
        should be named "linux")."

Which should it be, 2.4.6 or "linux"?

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-jmtd
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages lxr depends on:
ii  apache [httpd]            1.3.33-6sarge1 versatile, high-performance HTTP s
ii  perl [perl5]              5.8.4-8        Larry Wall's Practical Extraction 

-- no debconf information


--- End Message ---
--- Begin Message ---
Sorry to reply so late!

lxr is linux (kernel) specific.
You should use lxr-cvs for the new and non kernel
specific version. That version support a lot more
computer languages, directory structures etc.

To use the old version with other code bases it
is difficult (changes also in code), and not
supported in Debian.

For comment about the documentation:
you should read
1- create directory "2.4.6"
2- go in "2.4.6"
3- untar linux sources (usually named linux-2.4.6)
4- rename that directory to "linux"
so at the and you will have "2.4.6/linux/"

I'm not a English native speaker, so I don't know
how to rewrite in a better way.

ciao
        cate

--- End Message ---

Reply via email to