On 2/28/08, Jordan Moore <[EMAIL PROTECTED]> wrote: > I see two problems with requiring my users to download ZF separately: > > 1. It's not user friendly. Users should be able to download a single > archive, extract it, and install the application. > > 2. I can't guarantee compatibility with every version of ZF. > > Also, if I used the same logic with all included libraries for this > application, users would need to download a total of 4 external > libraries, and I would need to account for the varying versions of all > 4 libraries. > > By including the external libraries in my application's distribution, > users only need to maintain a single application, not an application > and 4 libraries.
So ship your product with a particular snapshot of ZF that you have tested thoroughly with. I think what Kevin means is that you should use ZF without modification such that, if necessary, someone could swap in an updated version. The rationale for that should be obvious. It's good advice. Under BSD you're welcome to fork ZF into your own thing. But given that ZF is specifically designed to be used in pieces and to extend components without needing to actually modify them, I think it would probably be a bad idea to create an incompatible derivation of the framework as a whole. The only justification for actually modifying ZF would be if you wanted to radically change things in fundamental ways. But in that case you might as well just start from scratch and create a completely new framework (and in fact complete re-writes are an inevitability as feature-creep and bloat starts to take over). Mike -- Michael B Allen PHP Active Directory SPNEGO SSO http://www.ioplex.com/
