On 12/24/06, Matt England <mengland@mengland.net> wrote:
> I see this stuff here:
>
> http://svn.haxx.se/dev/archive-2003-11/0446.shtml
> http://www.endrun.org/xr/svn/source
> I want to get native LXR (Linux Cross Reference) support for reading
> Subversion repos (it already does it for CVS repos) as per:
> https://sourceforge.net/tracker/?func=detail&atid=390120&aid=942911&group_id=27350
That would be great!
> Any chance the code from (<http://www.endrun.org/xr/svn/source>) can help
> get LXR to natively read Subversion like it can CVS? I'd like to help get
> the LXR folks started on this path if they show interest.
Well, I think it does exactly what you describe below: snapshot
indexing. At least, that's what I do at
http://hix.nu/subversion/lxr/source .
> Otherwise, I have to code-snapshot every change to my svn repos to get LXR
> views, which is doable, but I don't get any history/diff capability in LXR
> (or whatever it serves for CVS). Another thing I may try to do is use
> svn2cvs.pl to convert every svn change to cvs and then view that through
> LXR--a bit of an inelegant solution.
There is one problem with the assumption in the issue tracker you
quote: the person filing it has little knowledge of the internals of
LXR: I've tried to hack real subversion support into LXR, but that
turned out harder than I thought.
The problem is that LXR is modelled around changes in *files* instead
of changesets (ie versioned trees with changes).
I had some problems adapting it because of its lack of documentation
and thought that iff it's based on ctags anyway, it'd be possible to
write a much cleaner design... (probably learning from ViewVC for
syntax coloring / diffing.)
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 31 20:37:29 2006