Hi Andriesss, Thanks for pointing this out.
Gavin, I don't follow the logic of the FAQ answer. Being a newbie, perhaps I am overlooking something here, but I don't understand your comment that "The Zend Framework works together, as a complete unit." I understand their are various component dependencies, but I don't believe that I can't use Zend_Pdf, for example, if the _entire_ framework is not installed. If PDF generation is my goal, I don't care to have to install 15MB of framework just to use that piece. If anything I see that as being an inhibitor for framework use, especially as the core framework size grows (and it is, isn't it?). If I am not off my rocker about not requiring the entire framework to use individual components, wouldn't this open up the possibility for individual component packages? My understanding of the PEAR package format is that it support optional and required dependencies, including version dependencies. Wouldn't this feature shift "the responsibility and effort of integrating different versions of different components" to the PEAR package system, resolving the stated concern about end developer complications? Best, Michael -----Original Message----- From: Andries Seutens [mailto:[EMAIL PROTECTED] Sent: February 1, 2007 1:48 PM To: Michael Caplan Cc: fw-general@lists.zend.com Subject: Re: [fw-general] PEAR Channel Distro Michael Caplan schreef: > Hi Andries, > > I would think that distributing via a PEAR channel would help reach a > broader public. Was that not the case? > > Not to beat what I assume is a long dead discussion, I don't see the > connection between a need to release the whole codebase in steps VS > making each component available as separate PEAR packages. > > Best, > > Michael Hello Michael, Check out the fresh FAQ (Thanks Gavin): http://framework.zend.com/wiki/display/ZFUSER/Frequently+Asked+Questions Andriesss
