On Monday 11 Apr 2011 16:23:41 Matthew Weier O'Phinney wrote: > Zend_Loader_Autoloader actually understands a concept of versioned ZF > libraries already, which would make (2) an obvious choice. On the > following page: > > http://framework.zend.com/manual/en/zend.loader.autoloader.html > > look for the section entitled "Selecting a Zend Framework version". > Basically, have the latest version of ZF symlinked to a standard > directory, use the Zend_Loader_Autoloader class from that directory, > and then point it to the base directory and indicate a version you wish > to use. > > Zend_Application is also aware of this information, and you can > configure it with the keys "autoloaderzfpath" and "autoloaderzfversion". > > This approach allows you to have parallel ZF installs, while still > re-using them if several applications share the same versions. > Additionally, you can keep only the latest version of a given minor > release at a time -- these introduce BC breaks *extremely* *rarely* (as > in: only for security issues), which allows you to further minimize the > number of versions you retain on your system.
Hi Matthew, Thanks for the advice, I did not know about this new autoloader function. Also thanks to Simon and Marco for the responses! Besides the Zend and ZendX libraries I have a Doctrine, DomPdf and a custom ZF library as well. Our Doctrine and DomPdf libraries have a fixed version, but our own library is also versioned (with different version numbers than ZF). Is it possible to use this version select for ZF, another version select for our own library and a fixed version for 3rd party libraries? Or is this too complex? Regards, Jurian PS. I know minor and micro releases rarely cause BC breaks, but I'd rather be aware of it (and it does not happen) than the opposite ;-) -- Jurian Sluiman Soflomo - http://soflomo.com -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
