Re: Bundling third-party libraries

On Mon, 05 Jun 2006 08:24:58 +0200 sb@sebastian-bergmann.de (Sebastian Bergmann) wrote: > For PHPUnit I would like to be able to use third-party libraries like > the ConsoleTools component from the eZ components. I did not try eZ ConsoleTools, but what does it bring that cannot be done with: http://pear.php.net/search.php?q=console&in=packages&x=0&y=0 If php5+ only is a problem, we should put some effort to bring them to php5, but adding a external dependency sounds like the wrong way, no? > 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. The problem is that we do not allow non PEAR dependency in PEAR (and non *.php.net). There was good reasons for that. Licensing issues, packages availability, QA are some of them. I'm not saying that eZ has no QA or will be soon not available, only that we have no way to control them. That's true for any other 3rd party. > With regard to licensing this should be no problem as both PHPUnit > and the eZ components are licensed under the New BSD License. We have no way to be sure that no changes will be done on the license. Bundling a package solve the license problem, as the bundled package was released using a given license. This license is included as well. > I am looking for recommendation on how to package the eZ components I > need in the best practical way. I see only one way, include them in CVS and package them within the pear package. We provide warranties for our packages, available on our website, we can't (and will never be able to) provide these warranties for third party packages or sites. -- Pierre