Re: Bundling third-party libraries

From: Date: Mon, 05 Jun 2006 10:19:48 +0000
Subject: Re: Bundling third-party libraries
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-42765@lists.php.net to get a copy of this message
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 - we simply do not allow it - we require proof that no PEAR package could provide the required functionality with reasonable effort - we setup some guidelines about how to decide on a case by case basis - etc .. regards, Lukas

« previous php.pear.dev (#42765) next »