Rob Allen wrote:
Michael Caplan wrote:
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?).
Personally, I think that we should consider packaging up just library/
for each release in addition to the entire caboodle that we do at the
moment.
Certainly, on our production servers, we don't need demos/
documentation/, incubator/ or tests/. At the moment, we keep a copy of
library/ in our CVS system which is only about 6.5MB, compared to 52MB
for the entire thing (Zip distribution). A PEAR distribution would be
easier though.
Personally, I'm not too worried about having components we don't use in
there as you never know when a project will come along that'll require
something we haven't used so far. Also, if we run a third party ZF app,
we can be confident it'll "just work".
That makes it quite simple to have a pear package. There is a package to
generate the package.xml from a list of files or svn checkout.
Arnaud.
