[TYPO3-ect] [TYPO3-core] Wishlist from ECT

[Elmar Hinz]

Hi Ernesto,

> - global PEAR installation has nothing to do with TYPO3. The system
> administrator installs it in /usr/share/php or whatever directory the
> system default is. This information is given in php.ini and
> (include_dir=...) and every PHP application on that server can make use
> of it, including TYPO3
> 

This one is of minor interest. A successfull extension can't depend on
a system administrator getting in action first. But good as
additional solution for the professional agencies. The next one for the
masses.

> - for local PEAR installations the user has to install the "pear" TYPO3
> extension. The extension is installed in typo3conf/ext/pear/ and will
> create a typo3conf/tx_pear/ directory (local to the current

That is the innovative suggestion. Is this conform with the coding
guidelines?

> installation). In typo3conf/ext/pear/ext_localconf.php the extension
> will add that path to include_dir (using ini_set(...)) so that any
> "require(<pear-class>.php)" will find its stuff there. The "backend

That is the point that I am frightend of. The point that needs to be
reliable. Does this work in any case? Aren't there often cases were
this setting fails because of the providers settings, CGI/module
stuff, whatsoever. What tells experience about this?

> module" to install aditional pear modules will simply drop its
> additional pear packages in typo3conf/tx_pear/ (pointing the php_dir
> setting to that directory and possible calling the pear CLI to do the job).
> 
> Won't that work?

Maybe. I am not sure if it would work reliably under all circumstances. A
reliably working PEAR installation is the prerequest to get mature forms
libraries into action quickly and not only them. It's the default PHP
library system.

> 
> Cheers,
> Ernesto

Cheers

Elmar