Re: Bundling third-party libraries

Greg Beaver wrote:

Lukas Smith wrote:

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.

Well I presume there are some features in the PEAR packages that deal with console stuff, that are missing compared to ezc/ConsoleTools. However this is opening the flood gates. So we need to think carefully about how to approach this. We have had third party deps. I know that XML_Annotea bundled RAP and ADODB into CVS initially until I turned RAP into a PEAR package and made it work with MDB2. I am not sure if we have had a stable release of a package that dependent on a third party lib. Now just brainstorming ideas: - we just let PEAR developers bundle the entire package in that case - we mark some third party channels as legit for dependencies

The only way this could work is if we have an explicit, legal document from the third-party channel that the license will never change to a non-PEAR recognized license, or something along these lines.

You know this is impossible in the first place, as there is no legal PEAR entity. Besides that, nobody will ever agree to sign such a document either. However, we do ofcourse not intend to change the license to anything else than the "new BSD" license. regards, Derick