Sound sane? I can see splitting up the library base path into sections, but I'm not sure it's worth it. Now'd be the time to argue that, though :)
Makes sense to me to just store the path--keep it simple. As long as we've stored it away, anything using it later can chop it up into pieces itself if it wants too--anything we could have done in splitting it up, the consumer can do too. The only thing we really have to do is grab the info before it's too late--before something might have chdir'd, and before argv is either inaccessible, or could have been overwritten.
JEff
