Yes, the Zend Framework will only be released as a whole for these
reasons. Thus, the ZF will live as a single PEAR "component" at
pear.zfdev.com. There have been several previous discussions on this
topic, and the consensus agreed to keep the ZF synchronized, in a
harmonious whole.
Thus, the pear channel simply automates the approximation of downloading
the tarball and extracting into a well-known location, completing
replacing whatever previous version of ZF might have been installed.
For some environments, this will prove easier to manage and maintain,
especially with multiple ZF apps in multiple virtual websites on the
same server.
Cheers,
Gavin
Colin Ross wrote:
First Off, awesome. I love the idea, BUT.
I thought the zendframework was to be released as a whole, and
versioned/controlled in that sense.
I understand your rational behind it though, but i think (as a
community) we should try to stick to the idea of code reales of the
whole codebase in steps, lest we end up with "ZendFramework 1.01"
reallly being a mix of stable and not-so-stable components.
Not so say i won't be using it though :) good job, just trying to
avoid one of the few things i didn't like about PEAR.
Interdependencies of modules at different -levels of stability being
released together.
On 10/7/06, *Richard Thomas* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
http://pear.zfdev.com
Sooo close ;) packages should be available in the next week or so
--
Richard Thomas - CEO
Cyberlot Technologies Group Inc.
507.398.4124 - Voice
