Portable DXR/meeting 092608

Date: Friday Sept 26
Re: Project scope and requirement
People: James Boston (jboston), David Humphrey (humph)

15:01 < jboston> humph: What was that about auto-updating your dxr?
15:04 <@humph> say again?
15:06 < jboston> I eas reading the scrollback. You were saying something this morning about needing to 
                 refresh your dxr data.
15:06 < jboston> s/eas/was/
15:06 <@humph> oh, that's my source code indexing
15:06 < jboston> Yes. It sounds like you need some sort of automated process.
15:06 <@humph> when I build, I produce .sql files for all .cpp/.h units, and if one gets deleted, I need
               to yank it from my tree
15:06 < jboston> Funny thing. I was just thinking about how you get your data for the dxr today.
15:07 <@humph> the source index you mean?
15:07 < jboston> I think you need someone to automate the process for you.
15:07 <@humph> I do
15:07 < jboston> I think this falls within the scope of the prj thing.
15:07 < jboston> It may not be on a timeframe you need though.
15:08 <@humph> jboston: well, I'll do a hacky thing and you guys can clean up after me, yes
15:08 < jboston> Right now it's in a mysql database, right?
15:08 <@humph> correct
15:08 < jboston> Which you create from a mozilla build.
15:08 <@humph> I build, produce .sql files, then assemble and post process to get a sqldb
15:09 <@humph> the db gets build on each build
15:09 <@humph> built on each build
15:09 <@humph> brb
15:10 < jboston> If you wanted to got with the distributable extension idea you'll want it in an sqlite 
                 database probably, right? And you might want some way easy automated way to go from one
                 thing to other. I think that's in scope for my prj project.
15:13 <@humph> jboston: right.
15:14 < jboston> humph: So I think that creating/refreshing the database should be part of the prj project
                 I'm doing with samer, if that's something that interests you.
15:14 <@humph> for sure.
15:14 < jboston> Awesome.
15:14 <@humph> I have it working now, but the process should get added to a larger end-to-end content
               automation thing
15:15 <@humph> and my way is rough
15:15 < jboston> I envision a process where you start a script and at the end you get an up-to-date ready
                 to distribute extension.
15:16 <@humph> that's my goal.  I still think we should think seriously about putting all the content into
               the ext
15:16 <@humph> so we can push updates that way
15:16 < jboston> Yes. Samer and I were just talking about how updates could be done.