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

[Elmar Hinz]

> 
> Your latest contributions in this thread seem to be filled with anger
> for the core team but with little objective arguments with which you
> could convince us. Is there any still pending argument for
> typo3/contrib/pear you would like to share?
> 

Hi Ernesto,

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. 

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?

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?

Regards

Elmar