[Typo3-dev] TER, Extensions, PEAR integration

["Rafael Schär [beYou media]"]

Hi List,

I just got an email concerning my little pear integration extension 
"bypear". Right now, it is more an installation help for the pear 
framework, nothing more and runs only on linux system.
At the moment, the "bypear" extension is really not a mature extension.
But if there would be a need, there could be more intensive work on it, 
with a little help from my friends :-)

Me personaly, I had several times worked with the pear libraries and 
they are quite useful. It saves me a lot of time.

For those who understand german, see below the forwarded email.
I think, it may be a nice idea.

For those who only understand english, I try to translate it a bit (with 
my poor english, I am sorry about that ;-D

It's a mail from a person who works in the pear-team.
He wants to know about kaspers an others opinions about a smooth 
integration of pear.
Would it be worth enough to integrate pear and a dependendy management 
into the TER.
There could be something like this:
extension needs bypear und PEAR::Whatever.
Through an automatical installation using the pear installation and 
administration Framework, you could get the needed libraries.

He also talks about pear channels, but about this, don't ask me. I don't 
know anything about Pear Channels and the generic Pear Interface what 
he's talking about. Does anybody know more about that? Stefan?

What do you think?


Greetinx

Rafael


Forwared mail:
--------------

Hallo Rafael,

habe eben gesehen, daß du eine PEAR-Extension für Typo3 veröffentlich
hast. Da ich aktiv im PEAR-Team mitarbeite, freut es mich natürlich um
so mehr  :-)

Sag mal, hast du dir Gedanken gemacht oder evtl. auch mal mit Kasper
etc. gesprochen, ob es nicht möglich wäre allgemein auch
PEAR-dependencies für Extensions zu erlauben? Dann könnte eine Typo3-Ext
sagen "ich brauch bypear und PEAR::Whatever" oder so. Wäre imho eine
sehr saubere Lösung - zumal: Extensions in Typo3 durchlaufen ja ohnehin
ein zentrales Framework. Dort könnte also für Typo3-PEAR-Extensions auch
ein separater Include-Pfad gesetzt werden etc.
Oh, und PEAR bietet ja mittlerweile die Möglichkeit eigene Channels
anzubieten - ein generisches PEAR-Interface würde es so also ermöglichen
auf viele Pakete im PEAR-style zuzugreifen.


Grüße,
  Stefan

--- typo3.neufeind at speedpartner.de ---