[TYPO3-dev] Feature Request: Splitting localconf.php into hard and soft

[Martin Kutschker]

Joerg Schoppet schrieb:
> Hi list,
> 
> this is a feature request concerning the localconf.php file.
> I just want to make a discussion at first, before I'll open a feature request on bugs.typo3.org.
> 
> Problem:
> If you work in an enterprise environment, where a lot of people develop on a typo3-instance, you may need to use a version control system like cvs or subversion to track all kind of changes.
> Through the possibility of "INCLUDE_TYPOSCRIPT" you can put the most TS-Code under version control.
> The last (big) problem I see is the localconf.php file. This file is, in my opinion, the most important file (one wrong change and the complete typo3 stopps). The problem with this file is, that each extension install and deinstall and extension-configuration writes in this file, so it is nearly impossible to make a wise external version control.

How is the external versioning to be triggered?

Both the installer and the ext. manager would have to do a checkout/commit 
regardless of how many parts you split localconf.php into.

But there is relief:

There is only a single function in TYPO3 that writes to localconf.php:
  t3lib_install->writeToLocalconf_control()

The new version of TYPO3 4.0 already writes to a temp file first. Write an 
XCLASS that does the correct procedure for your version control system.

Masi