Re: [Lxr-dev] Updates?

[Paul S. <ps...@ne...>]

On Mon, 2007-06-18 at 16:45 +0200, Arne Georg Gleditsch wrote:
> Paul Smith wrote:
> > I would love to do some more work on LXR but I really don't want to get
> > too far out in front of the official codebase; my experiences with this
> > have been universally negative (more work for everyone, in the best
> > case).
> 
> On this tangent: in the process of trying to resolve my own scalability
> issues with lxr.linux.no, I have a private lxr codebase that has
> diverged non-trivially from mainline.  (And I do regret that, my
> experience is in line with Paul's here...)  Still, I do hope to put this
> into production on lxr.linux.no in the near future.  Once that happens,
> I'd be interested in assessing the actual gap to mainline, but in the
> mean time the code lives in a private repository of mine under the name
> "lxrng".  If any of the movers and shakers in the lxr-mainline camp feel
> uncomfortable with me using this name in public as well, I'd like to
> know.  I do feel I have a certain historical claim to the "lxr" name,
> but at the same time I'd like to avoid stepping on peoples toes.

My only concern about this is that if LXR does manage to bring your
enhancements back into the main codebase (as hopefully it will!) then
we'll have an "lxrng" which is less up to date than the main "lxr",
which would be confusing to all I would imagine.

Maybe we can find a less evocative name, something like "lxralt" or
"linxr" or something like that, that doesn't imply "next
generation" (even if, for the time being at least, it really is!)
Ultimately, however, it doesn't bother me much either way.  Whatever
happens will be survivable.


Also, I second Max's interest in seeing the code changes, or at least a
list of enhancements/changes.  I don't know if you've had a chance to
follow some of the modifications I was suggesting a month or two ago,
but I wonder if any of your changes are in those areas.

My main interest at this time is (a) collecting the various bug fixes
that are going around and integrating those, (b) cleaning up the class
interface to the back ends to allow new ones to be more cleanly created
(I have at least on back end that I'd like to write, that is tricky with
the current interface), and obviously (c) getting a new release out
there.

(c) might most profitably be done multiple times (once after (a) and
again after (b) for example).


Cheers!

-- 
-----------------------------------------------------------------------------
 Paul D. Smith <ps...@ne...>                       http://netezza.com
 "Please remain calm--I may be mad, but I am a professional."--Mad Scientist
-----------------------------------------------------------------------------
      These are my opinions--Netezza takes no responsibility for them.