[TYPO3-ect] Testing the PEAR installer

[Daniel Brüßler]

Hi Elmar,

nothing is impossible :-) We'll find a good way.

kind regards
Daniel

Elmar Hinz schrieb:
>>> B.) Channels. pear and pecl are preconfigured. I think it would be nice
>>> to have same more. Which channels are interesting?
>> Robert says he likes to use eZ Components also for 5. Question is if we
>> use the channel ezc in the pear-extension, or if we have a
>> "ezc"-extension just for ezc-components.
> 
> When we put EZ components into an own extension, they will soon be out of
> date and it costs extra time to maintain it. 
> 
> How about an ezc add-on to pear: pear__ezc?
> 
> Such an extension would simply trigger loading of the recent ez libs via
> pear channel into the central pear repository,  where they can be
> maintained with the pear manager. Something in that direction.
> 
> But you suggested to implement pear dependencies into the extension manager.
> In that case an own ezc extension maybe becomes unnecessary. You would
> write something like this into the extension setup:
> 
> 'constraints' => array(
>         'pear://components.ez.no/DatabesSchema' => '4.12.7-'  
> )
> 
> That should load the recent ez DatabaseSchema package. But conflicts would
> occur when different versions are required by different extensions:
> 
> 'constraints' => array(
>         'pear://components.ez.no/DatabesSchema' => '4.12.7'  
> )
> 
> 'constraints' => array(
>         'pear://components.ez.no/DatabesSchema' => '4.13.8'  
> )
> 
> I fear that couldn't be solved because different versions can't be used in
> parallel. The classes use the same namespace.
> 
> Regards
> 
> Elmar
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>