Re: Bundling third-party libraries

Sebastian Bergmann wrote:

For PHPUnit I would like to be able to use third-party libraries like the ConsoleTools component from the eZ components. Given the fact that I do not want non-optional dependencies starting with PHPUnit 3 and that this dependency would be non-optional I would have to bundle this third-party (ie. Non-PEAR) library with PHPUnit. With regard to licensing this should be no problem as both PHPUnit and the eZ components are licensed under the New BSD License. I am looking for recommendation on how to package the eZ components I need in the best practical way.

The brute way would be to import a version directly in the cvs tree. You would then update it according to your needs (like what HTML_Ajax did with JSON). Pros: it makes it easy to use the cvs version for anybody., you control the version and have less nightmares about people using different versions. Con: you need to update it yourself. Another way would be to have a script that creates the package.xml from the filesystem. You would keep a local copy of the third-party library and only package it when about to do a release. Pros: update path for the library is easier. Con: it makes it a bit harder for people to use the cvs version (providing snapshots would solve that) These are two pre-morning coffee ideas, Arnaud.