> > No, I think you're mixing up compile-time and run-time values -- and > also reading too much into the file names. "make.conf" should really > rather be called "portage.conf". That would make much more sense IMHO. > :) >
As long as the source is the documentation, it should be possible by concept to read in filenames. I think you are right, that portage.conf would be the natural name. Al