30 Mar
2012
30 Mar
'12
4:04 p.m.
On 03/30/2012 02:50 PM, Darrell Anderson wrote:
After searching the entire source tree, I concluded
those vimrc and config.log files are from somebody on the Trinity team.... :) My clues are
the vimrc files are exactly the same (same person) and the config.log files all include
references to /opt/trinity. I don't use vim and I'm paranoid about working
directly within the source tree (I always make copies). I counted 16 config.log files and
three vimrc files. Not many. I'll purge them.
Excellent work -- and that's just the tip of the iceberg. We need somebody with
autofoo and libtool experience to come up with a list of UNNEEDED files that are
leftovers so we can just remove the remainder of the garbage as well.
When I try and learn how these things works, having old build files in the tree
just provides more rabbit trails for me to follow. If I were more knowledgeable
on how this stuff worked, then I could help with the list, but when i look at
dirs full of .in .in.in .in.in.h, etc..... I don't know what's old what's
new,
etc.. I've read about the process and have a feel for it, but not good enough to
know 'ah hah!' this piece of autofoo is a leftover and not used.
Not a high priority, but I'll try and keep documenting what I find.
--
David C. Rankin, J.D.,P.E.