Thread: [Lxr-dev] Updates?
Brought to you by:
ajlittoz
From: Paul S. <ps...@ne...> - 2007-06-14 01:24:27
|
Hi all; Is there any news on a new release, or applying any of the patches, etc. that are available for LXR? The last time I posted here there was a large flurry of excitement that seemed promising, but it settled down and it's been largely quiet ever since. Are there plans? Are more hands needed to make releases/apply patches/update bugs/perform drudge work? I'd be willing to put in some elbow grease, esp. short term, to get the wheels turning again (I'd need access in SF for these tasks of course). We just installed a new LAMP box and I'm about to start migrating my test install of LXR over to this system to be a "real" environment, and I'd sure like to have some of the enhancements I've mentioned before (not the least because we use an SCM tool which is not currently supported by LXR and I'm toying with the idea of implementing a backend for it). 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). Let me know; cheers! |
From: Malcolm B. <mal...@gm...> - 2007-06-14 23:02:45
|
Hi, Paul Smith wrote: > Hi all; > > Is there any news on a new release, or applying any of the patches, etc. > that are available for LXR? The last time I posted here there was a > large flurry of excitement that seemed promising, but it settled down > and it's been largely quiet ever since. Indeed > Are there plans? Are more hands needed to make releases/apply > patches/update bugs/perform drudge work? I'd be willing to put in some > elbow grease, esp. short term, to get the wheels turning again (I'd need > access in SF for these tasks of course). Plans yes, action no :-( I'm afraid I have very little time for LXR these days, hence the lack of releases, patches etc. If you'd like to start doing some of this then you'd be very, very welcome. Drop me a mail with your SF details and I can get you set up. > > We just installed a new LAMP box and I'm about to start migrating my > test install of LXR over to this system to be a "real" environment, and > I'd sure like to have some of the enhancements I've mentioned before > (not the least because we use an SCM tool which is not currently > supported by LXR and I'm toying with the idea of implementing a backend > for it). More backends welcome - some of the recent work on BK/Git should make implementing this easier, since at least what has to be done is now documented! Malcolm |
From: Arne G. G. <ar...@gl...> - 2007-06-18 14:46:00
|
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. -- Arne. |
From: Maximilian W. <ma...@rf...> - 2007-06-18 17:32:44
|
Am Monday, den 18 June hub Arne Georg Gleditsch folgendes in die Tasten: Hi! > 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. Can you put your Code into a public accessable GIT or something else, so one can pull your version an have a look at the changes? You could create a branch pimpMyLxr or so :) Ciao Max -- Follow the white penguin. |
From: Arne G. G. <ar...@gl...> - 2007-06-25 08:26:58
|
(Sorry about the delay; real life intervened...) Maximilian Wilhelm wrote: > Can you put your Code into a public accessable GIT or something else, > so one can pull your version an have a look at the changes? For sure. lxr.linux.no is due to move to new, dedicated hw in the near future, and I was hoping to put up a beta version with source and the like on that one. I was hoping to have this done by now, actually. If it looks to take much more time, I'll put the source up somewhere else in the meantime. -- Arne. |
From: Maximilian W. <ma...@rf...> - 2007-12-07 00:48:40
|
Am Thursday, den 29 November hub Arne Georg Gleditsch folgendes in die Tasten: > Arne Georg Gleditsch wrote: > > For sure. lxr.linux.no is due to move to new, dedicated hw in the near > > future, and I was hoping to put up a beta version with source and the > > like on that one. I was hoping to have this done by now, actually. If > > it looks to take much more time, I'll put the source up somewhere else > > in the meantime. > Famous last words... For real this time, lxr.linux.no is due to move to > new hardware and experimental code pretty soon. For those of you who'd > like to have a look at what that looks like, lxr-test.linpro.no is > operational with what's going to be the new site. (The path to the git > repo on the main page needs adjustment until dns is updated.) http://lxr.linux.no seems to be updated now :) Looks nice. Kinda 'web 2.0' ;-) Has the diff feature gone or did I just miss it? Ciao Max -- Follow the white penguin. |
From: Arne G. G. <ar...@gl...> - 2007-12-09 19:30:49
|
Maximilian Wilhelm wrote: > http://lxr.linux.no seems to be updated now :) So it is. Seems to be running fairly ok, although there are a few performance hotspots that could do with a bit of attention. > Looks nice. Kinda 'web 2.0' ;-) Thanks. Yeah, kinda. :) > Has the diff feature gone or did I just miss it? It's gone for the time being. I had planned to implement it before switching lxr.linux.no, but decided it had been held up for too long. I'm planning to reimplement the diff feature alongside a history feature, where you could open a drop down box of the last 10-15 viewed files and either jump back to them or compare them to the currently open file. (As the old implementation of the diff feature depended on the version and arch variables, the number of available dimensions you could show differences in were halved when the "arch"-variable (or rather, the "arbitrary user-specified path variables") feature was removed.) -- Arne. |
From: Paul S. <ps...@ne...> - 2007-06-18 17:49:18
|
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. |
From: Arne G. G. <ar...@gl...> - 2007-06-25 08:47:56
|
Paul Smith wrote: > 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. Yes, some of them are. One of my main concerns have been scalability, genxref-time, so there are a couple of changes in that area. I'm using postgres' copy for populating some of the tables, for instance. Also, the freetext indexes are incremental (using Xapian) in the hope that this will scale better (both run-time and space-wise) than one full index for every release. (My ambition is to have all 7-800 releases of the Linux kernel referenced and indexed on lxr.linux.no.) Xapian also makes it easier to provide line number information with the search results. The identifier lookups attempt to consider the scope of the reference you're following. The web interface has been redone. > 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. I agree with your agenda. Also, if you want to get a release out the door as soon as possible, I'd suggest you ignore me for the time being. (I'd be interested in hearing more about your specific concerns regarding (b), though.) -- Arne. |
From: Paul S. <ps...@ne...> - 2007-06-27 18:04:48
|
On Mon, 2007-06-25 at 10:47 +0200, Arne Georg Gleditsch wrote: > > (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) > (I'd be interested in hearing more about your specific concerns > regarding (b), though.) There's an email from me whinging about the structure of the File backend class interface and burbling about the way I would prefer to see it structured. Let me look... start here for example: http://sourceforge.net/mailarchive/message.php?msg_name=1174269877.16513.12.camel%40homebase -- ----------------------------------------------------------------------------- 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. |
From: Jan-Benedict G. <jb...@lu...> - 2007-06-25 08:54:29
|
On Mon, 2007-06-25 10:47:47 +0200, Arne Georg Gleditsch <ar...@gl...> w= rote: > index for every release. (My ambition is to have all 7-800 releases of > the Linux kernel referenced and indexed on lxr.linux.no.) Xapian also Dito. This is why we started the drop-down thingie for versions at some time. Max has the most up-to-date patches. Worked mostly, IIRC, but ISTR a problem with /diff. MfG, JBG --=20 Jan-Benedict Glaw jb...@lu... +49-172-7608481 Signature of: Gib Dein Bestes. Dann =C3=BCbertriff Dich sel= bst! the second : |
From: Arne G. G. <ar...@gl...> - 2007-06-25 09:04:55
|
Jan-Benedict Glaw wrote: > Dito. This is why we started the drop-down thingie for versions at > some time. Max has the most up-to-date patches. Worked mostly, IIRC, > but ISTR a problem with /diff. As it is, the diff functionality depends on the different "axis" defined for a tree (which are usually "version" and "arch", since that's what the default config uses). I've come to think this is broken. I'd like to see your browsing history available as a drop-down, where you can choose to diff the currently viewed file against any of the, say, 5 last files you've visited in the current tree. I want to toss out the user-defineable variables altogether, and just keep "version" as an integral component. I think they clutter up the interface, are not horribly useful and, in the rare cases where they could be useful, are too complicated to actually use. -- Arne. |
From: Arne G. G. <ar...@gl...> - 2007-06-27 20:36:09
|
Paul Smith wrote: > On Mon, 2007-06-25 at 10:47 +0200, Arne Georg Gleditsch wrote: >>> (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) > >> (I'd be interested in hearing more about your specific concerns >> regarding (b), though.) > > There's an email from me whinging about the structure of the File > backend class interface and burbling about the way I would prefer to see > it structured. Let me look... start here for example: > > http://sourceforge.net/mailarchive/message.php?msg_name=1174269877.16513.12.camel%40homebase Thanks, I remember reading it now. Yes, I agree that independent objects per file is the way to go. It's what I've got in my tree, anyway. -- Arne. |
From: Paul S. <ps...@ne...> - 2007-06-27 21:02:41
|
On Wed, 2007-06-27 at 22:37 +0200, Arne Georg Gleditsch wrote: > Thanks, I remember reading it now. Yes, I agree that independent > objects per file is the way to go. It's what I've got in my tree, > anyway. If you've already done work like this then definitely I'd like to see your stuff before committing lots more effort to modifying the existing LXR. -- ----------------------------------------------------------------------------- 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. |
From: Arne G. G. <ar...@gl...> - 2007-11-29 11:49:27
|
Arne Georg Gleditsch wrote: > For sure. lxr.linux.no is due to move to new, dedicated hw in the near > future, and I was hoping to put up a beta version with source and the > like on that one. I was hoping to have this done by now, actually. If > it looks to take much more time, I'll put the source up somewhere else > in the meantime. Famous last words... For real this time, lxr.linux.no is due to move to new hardware and experimental code pretty soon. For those of you who'd like to have a look at what that looks like, lxr-test.linpro.no is operational with what's going to be the new site. (The path to the git repo on the main page needs adjustment until dns is updated.) -- Arne. |