[TYPO3-ect] Testing the PEAR installer
Elmar Hinz
elmar.DOT.hinz at team.MINUS.red.DOT.net
Fri Jul 13 13:09:45 CEST 2007
>
> I like that way, because so no admin has to care about that. What do you
> think about this easier version in a header of any extension:
>
> require_once (t3lib_extMgm::extPath('pear'). 'pear-init.php');
> pear-init();
Hi Daniel,
that's right. It should be as simple as possible. No admin should care
about. No extension developer should care about.
That's why I am thinking about the file: EXT:pear/ext_localconf.php.
If an extension depends on pear this file is always included before the
extension itself. So it should be a save and general way to set it there.
Is that right?
IMHO this line would do the trick:
set_include_path(get_include_path() . PATH_SEPARATOR .
t3lib_extMgm::extPath('pear')' . 'PEAR/');
Regards
Elmar
More information about the TYPO3-team-extension-coordination
mailing list