Closed Bug 13849 Opened 26 years ago Closed 6 years ago

merge mozilla.org LXR customizations to SourceForge LXR

Categories

(Webtools Graveyard :: MXR, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: endico, Unassigned)

References

Details

The new version isn't released yet but I need to install and test drive it. Probably need to re-implement some customizations if there are some they didn't take. Generally make sure things work.
Blocks: 5012
Blocks: 5597
Blocks: 13812
Status: NEW → ASSIGNED
Hey, how's this going? Do you think landfill could host an lxr testbed?
OS: Solaris → All
Hardware: Sun → All
what's the situation on this? If this was for updating lxr.mozilla.org, Myk just did it the other night, to pick up the raw=1 fix.
I only updated the one file that got fixed, and I didn't sync it with the trunk of lxr development but only with the newer version of the file in mozilla.org's repository.
This assigned bug hasn't been touched in a couple of years. This is me poking it to see if it should be unassigned/helpwanted.
OK, this sounds like this bug means to get mozilla.org's LXR updated with the current official LXR.... Brad: Am I correct in thinking I remember that you were working on doing this?
I did some personal poking at the 0.9 version of lxr that's on sourceforge and found it unusable. I took that codebase and have started essentially a rewrite but it's not really useable yet.
fwiw landfill is now hosting an mxr or two (in addition to an lxr for bugzilla) See <http://landfill.mozilla.org/mxr/>. I've started resurrecting patches and putting them on /mxr-test/. I've setup trees for most things imaginable. I've also started triaging bugs. I don't have glimpse search working but find and ident work (ident works better on mxr-test). Nor have I setup automatic updates of the files or indexes, I'll probably do that next sunday (I'm traveling a lot this week).
QA Contact: timeless
Any progress on this? There are also other efforts where people have patched LXR to work for them, for example http://openit.disco.unimib.it/
Dawn, do you mind if bear takes this? If not, I think the summary should be changed to something like "Merge our LXR changes with SF LXR and move all our open bugs to their bugtracker". This should be the first stage of a two stage process to replace our version of LXR with the version developed on SourceForge: http://sourceforge.net/projects/lxr This bug can deal with merging all the relevent changes we've made to our version to LXR with the SF version, and with moving all our open LXR bugs to the SF bug tracker. The LXR compontent in bmo should then be removed/disabled if possible. Once this is done, a separate mozilla.org/Server Operations bug can be opened to have LXR removed from/frozen in our repository, and the version at lxr.mozilla.org upgraded to the SF version. Thoughts?
i have a bunch of changes on mxr-test which i want to land, but i don't think dawn's currently active here.
Dawn's not around these days. Jonathan, that sounds like a good plan. Reassigning to bear and updating summary. timeless, you should land your changes in the SF LXR.
Assignee: endico → bear
Status: ASSIGNED → NEW
Summary: upgrade to new version of lxr → merge mozilla.org LXR customizations to SourceForge LXR
This is my plan of attack: 1. get the sourceforge version and install it along side of the mozilla version 2. run diffs to see how different they really are 3. knock the low hanging fruit 4. report here and get some feedback 5. rinse and repeat
I don't know if the list of all the changes that have gone into the version of LXR in Mozilla's CVS is useful to you, but here it is anyway. http://bonsai.mozilla.org/cvsquery.cgi?dir=mozilla%2Fwebtools%2Flxr&date=all
Status: NEW → ASSIGNED
QA Contact: timeless → lxr
Assignee: bear → nobody
Status: ASSIGNED → NEW
Should this be closed as a WONTFIX? Or at a minimum, de-prioritized from "P3" to "P5" or "-"?

mxr is gone, mass closing.
https://searchfox.org/ is a much better alternative.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.