TYPO3 Core

You can consider using "Global Extension" - that will place the extension in typo3/ext. Check the Install tool for activating the feature.

Imho those php cache files should be put into the caching framework with a PhpFrontend (would be useful in the autoloader, too) in the long run.

I've hacked around on this topic a bit, but it's pretty tricky to get right (you'll run into scope problems and some hairy bootstrap chicken-egg things).

I'm -1 for just putting these files to somewhere else and make the location configurable as this compilcates the TYPO3 boostrap even more.

This issue is a "won't fix" until major work to the bootstrap logic was done.

Ok, I knew this was going to be tricky. Caching (using the caching framework) sounds like a cool solution. Maybe refactoring the "config_default.php" could become a subtask/next step of refactoring the bootstrap process (init.php).

For now I agree with a "won't fix".

Resolved, won't fix.

Thanks for your reply, Arjen. As discussed, we will not tackle this issue now, it can only be solved as a side-effect with a serious re-factoring of TYPO3 bootstrap.