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

[Ernesto Baschny [cron IT]]

Elmar Hinz wrote: on 12.02.2007 15:02:

> as I already mentioned. It is not important to have this or that path. It
> is important to have a reliable include path for this directory. I don't
> see how a trustworthy path could be set from an extension. But maybe you
> can help.

What do you mean with "trustworthy"?

> I can see how a trustworthy path can be set during setup. But it would be
> a little funny to set a path for an extension that is still not installed.
> Woudn't it?

Why would you need that? If "pear" extension is not installed, there is
no need to have a path. Once you install the pear extension, the
extension itself can generate the path as it wishes.

> Then an extension typically carries the content and is not a repository
> itself. PEAR is itself an extension system. So it would logically
> positioned side by side with the TYPO3 extension folder instead of being
> an extension folder itself.
> 
> First install an empty PEAR folder as extension with the questionable
> include path. Then install third party PEAR extensions into it possibly
> controlled by the forth extension that depends on it. Guess that can
> become pretty cumbersome. Do you see any success in this?

I have imagined it a bit different, maybe I am a bit naive:

- 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

- 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
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
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?

Cheers,
Ernesto