[TYPO3-ect] TODO: PEAR installer/ uploaded
Daniel Brüßler
info at -remove-patchworking.de
Thu Jul 12 09:50:33 CEST 2007
Hi Joerg,
oh, this can be a great workaround for the fact that Extension Manager
cannot check the dependencies in the moment.
Just brainstorming:
When jr_pear_mail depends on the pear-extension it could call the
pear-extension that it wants to use PEAR::Mail::1.1.14 . That call is
not good in a special BE-module because every such extension would need
that. It's not good as CLI-call because an admin had to config that.
Could be good to do that call when first used in FE.
The call could be so:
* check "installed"-flag if "Mail" is installed
* instantiate class pear_get (not existing yet)
* call function install with parameters "Mail" and "1.1.14"
* set "installed" flag, that it IS installed now and that pear is not
needed to call again
So there would be a REAL dependency for the PEAR Mail package.
When that works good the Extension Manager can be changed so, that it
makes that call while installing something that needs Mail >= 1.1.14
Crazy I know but what do you think about that.
kind regards
Daniel
>> And what about these extensions. Do we still need them ?
>> jr_pear_mail -> Joerg Schoppet
More information about the TYPO3-team-extension-coordination
mailing list