common config.cache for ebuilds?

[proxy]

just a thought, but it seems to me that we could really cut down on package installation time by having a share config.cache. It would not be trivial to setup perfectly, but i mean, most of the tests are for standard C/system configuration, lib locations.... stuff that rarely changes.

if we had a common config cache, that was diff-ed after each emerge with the cahced results of that new emerge. future emerges could practically skip most of the configure work.

anyone have any thoughts on this?

proxy