On Fri, 2007-03-16 11:38:34 -0400, Paul Smith <psmith@...> wrote:
> Is anyone actively working on this project? I see some commits went in
> in January, but there are a lot of bug reports that aren't being managed
> (many duplicate bugs and no one seems to be closing them) and a number
> of the bugs being reported are already fixed in CVS, but there's no
> release available, or comments about when a release might become
> available. There are also a few patches that look like they (or the
> ideas they implement) could be helpful.
AFAICT, there's no "active" work being done at this time. The last
patch I saw popping up here on the list was some perl5 compatibility
stuff for callin exit(), IIRC (which is still unreviewed.)
> I have done some work in my local version which has a big performance
> increase for my source tree, using swish-e (it won't help everyone's
> environment: it really helps with handling non-text files).
Great. Care to send some patches for review?
> I've also found a few other issues, like not all my header files are
> getting hyperlinked properly.
Only found the issue or also a fix?
> Before I go too much farther with enhancements/fixes I'd like to have an
> idea on the status of LXR; is it still viable? Are there thoughts about
> a new release (even just a 0.9.5, not 1.0)? Is there a need/desire for
> new developers on the team? Or, is everyone just using their own
> customized version and they're happy with that?
For years (at least for five years or so), there's only one "release"
I'd tell people to download: CVS HEAD. So you shouldn't take a
released tarball to start. I also think that we'd place a new
release. At least there was the GIT backend added, which (taken that
the initial scope of LXR is to visualize Linux kernel source code) I
think is a somewhat important addition.
LXR is, to my knowledge, also the only project in this area, that
works. So that's a definitive answer (at least from my point of view)
that you're right in starting hacking right here if something doesn't
work for you, or that you place bug reports.
In the case of bug reports, I'd suggest sending them to the list and
not to SourceForge's bug tracker. I don't think anybody pays too much
attention to it....
> Should I start looking more seriously at alternatives such as OpenGrok,
You may choose whatever tool fit your needs, but I'm not really
thrilled by OpenGrok. Just look at their web page
(http://www.opensolaris.org/os/project/opengrok/). The comparison to
other projects is totally bogus. As we'd say in German, they're
comparing apples to pears.
cscope/ctags look pretty poor compared to LXR and OpenGrok, but
they're focussing a totally different problem. It's just not their
business presenting web-pages with source code! Finally only look at
LXR vs. OpenGrok:
Definition search: "the feature may be partly present" in LXR? What
the heck?! I think they've been on crack when
they wrote that...
History search: LXR is /not/ a history browser. It's ment to
give access to well pre-defined releases of
source code. If you want history display, use
ViewCVS or one of the other history displaying
tools. Not our business!
Shows matching lines: What's this feature, exactly? LXR can show
diffs between releases, but honestly, I don't
know what they mean here.
query syntax like AND,
OR, field: LXR doesn't do searching itself. Not LXR's
business. LXR is more flexible by using
external search engines. Buy a Google
appliance (yes, really, you can have your own
Google!) and we'll manage to stuff the sources
in there! But well-working searching is not
something that should be too deeply built into
any tool, because there are better tools
Incremental update: We do that.
Interface for SCM: Erm, without interfaces to SCMs, we'd face a
hard time displaying anything, right? So we
don't have an SCM interface? Heck, I've been
working on the wrong project :)
open source: Huuuhuhh?! Anybody at home? LXR is GPL? I
always thought GPL _is_ an Open Source
download: They're right. We don't have that. Probably
because nobody ever thought it would be
useful? Need it? No problem. That'd be easy to
Changes at directory
level: I don't understand this. What's it exactly?
Multi language support: Just a matter of placing customized template
files. But right now, we only have the English
So that comparison really looks bogus to me. But they're not
mentioning some parts that are somewhat imprortant to me:
OpenGrok uses Java (thus has a requirement to a language that probably
needs non-free interpreters) while LXR just uses simple plain
OpenGrok is licensed under CDDL, while LXR is GPL. So OpenGrok ships
with a GPL-incompatible license...
Finally, OpenGrok needs a Tomcat (or equivalent) running, while LXR
just needs a simple Apache instance.
So have a look at both projects and decide which of those serves your
Jan-Benedict Glaw jbglaw@... +49-172-7608481
Signature of: http://perl.plover.com/Questions.html
the second :