Bryce Lohr wrote:
Having a PEAR channel would seem to me (from an end-user perspective) better than having to learn an additional CLI tool that essentially does the same thing PEAR already does: put some PHP code on my system. As Paddy mentioned in another post, PEAR has quite a bit of functionality. Many PHP developers are already familiar with it. What would a ZF-specific tool need to do that PEAR could not do already? If there's some specific requirement that PEAR can't meet, then that seems like a good reason to consider a custom tool.
If there is some specific requirement PEAR can't meet then there is an alternative of contributing the needed modifications back to PEAR. All-in-all it's what open source is all about.
I'm in favor of using long established standards and code reuse rather tahn next proprietary release management platform. I vote for PEAR.
Also, none of this should preclude keeping the existing tarball/zip download.
Exactly. -- Michał Minicki aka Martel Valgoerad | [EMAIL PROTECTED] | http://aie.pl/martel.asc =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "Idleness is not doing nothing. Idleness is being free to do anything." -- Floyd Dell
