In meta-data, strength !
> My thought was to emit a file from the SQL database that has relative paths to the files where Exclude_File='Y' OR Third_Party='Y'
That's the sort of thinking I like.
Yes, --ignore-file and --ignore-directory would do that.
> and drop that in the root. Ack would somehow know to read that file and not search those files.
There is a commandline arg --ackrc=file to specify an alternate ackrc
file; that might be useful.
> It seems like I might be able to use a project level .ackrc file
IIRC we added that in Ack2.0
> (didn't know about those before today)
> with a bunch of --ignore-file directives - but there might be thousands and thousands of them and I worry about performance here.
Thousands of small ackrc files might perform better than one huge one.
I don't recall if Rob or Andy have benchmarked that.
> Is this abusing this mechanism in ack?
Well probably yes :-) but that's what ack is for, to take abuse that
otherwise would be absorbed by our eyeballs using grep. :-)
> Other thoughts?
One thing for you to look out for is if any of the projects you import
already has project or homedir .ackrc files.
If you have a backup of DEV system disks, the "user directory" $HOME
.ackrc files will become project .ackrc as you traverse the tree.
You may need to rename or remove those to avoid conflict.