I’m sure this isn’t the first time this question has been asked but will Zend Framework ever be distributed via a PEAR channel? Some of you might try to point me to this non-Zend site claiming to do just that but it is falls a bit short. That site simply bundles all of ZF as a single package. Someone else may point me to this outdated article about an unofficial ZF PEAR channel. It too only distributes the entire ZF which begs the questions who really need the entire Zend Framework. More importantly why hasn’t Zend provided an official PEAR channel? In my search for an answer I found this response from “bkarwin”: No, we have no plans to offer ZF under a PEAR channel or other piece-by-piece distribution method. Assuming bkarwin was working in some half-official capacity at Zend I’d simply ask “Why not?”.
From Zend’s marketing standpoint I suppose bundling it all makes sense but it seams to me there is a good middle ground being missed. Why not create each ZF component as a separate PEAR package then have a single PEAR package called Zend Framework that simply lists all the individual ZF components as dependencies. It’s the perfect middle ground allowing us the ability to install all of ZF or just the parts we want to use.
To Zend’s credit ZF is very much community driven but the fact they don’t use PEAR as a packaging mechanism can send the unintended message that Zend may have a bit of the Not-Invented-Here (NIH) complex. I don’t believe that is the case but it’s hard not ponder that possibility. Greg Beaver and the many other great contributors to the core PEAR package which handles the building and management of PEAR packages have a great thing going and the fact ZF isn’t using it is a bit frustrating. Case in point, what happens in the even of security fixes for one ZF component? Currently you’d have to manually patch files or wait patiently for all of ZF to be rebundled. Why do that when you could patch the component and quickly publish the fix to the channel allowing us all to apply the fix with a simple command line?
So the question I have is why hasn’t Zend published an official ZF PEAR channel? What is it about the so-called piece-by-piece method of distribution model that is so wrong? Having built and setup our own PEAR channel here at the State of Iowa, I can attest this can be put in placed and managed fairly easily. Please help me understand why this isn’t a good idea.
I followed the mailing list for a while and I believe the issue is that PEAR isn’t very ‘shared hosting friendly’ and ZF is aiming to be an easy install for anyone regardless of environment.
When was the last time you tried to get your shared host to install (or update) a pear package for you? =(
You can always do a manual install. Remember PEAR packages are nothing more than tarballs. If that is the biggest argument, I’d say the Zend folks could very easily provide two forms of packaging.
–Tony
I haven’t been following closely the ebbs and flows of this debate in ZF circles. But what I have gleaned is that there is a general rejection of componentizing ZF.
The (failed) community driven project to package up ZF into one monolith package provided no value. Why would i use that over the many other ways I can access the complete framework? Using SVN externals is more convenient if I am committed to the entire framework.
But, I don’t want the entire framework, especially as it grows in size and become another PEAR like clearing house that includes everything under the sun, including the kitchen sink (albeit in a much more coherent fashion).
To leverage the true power of PEAR packaging would require the breaking down of ZF into components. The position of the ZF team that I understand is one of “all or nothing.” I frankly don’t get this. I just don’t see how componentizing ZF is impossible or gravely limited because of technical barriers, or sound social reasons.
Arguably, the value of ZF would be much greater if I could easily choose what libraries I needed, and let some sort of great packaging and distribution system handle dependencies, installation and updates.
I am using ZF in several projects and couldn’t imaging workign without it. But not supporting PEAR packaging and channels just makes using it not as convenient.
re: NIH in the Zend Framework: one need only look at how much they’ve re-invented…
I couldn’t agree more, I think it’s a massive oversight that individual Zend libs are not available via the PEAR installer. I suppose if someone dedicated the time to packaging it all, the ensuing popularity of the format might change some minds.
Personally I mix and match, choosing whichever is the best component for the job, and use Zend_Cache but am forced to install the whole Zend_* monster via PEAR to access it .. bit primitive.
I officially got an unofficial answer regarding this.
In short, don’t hold your breath. For better or worse…(worse)
–Tony