Re: Bundling third-party libraries
| From: | Derick Rethans | Date: | Wed, 07 Jun 2006 14:29:28 +0000 |
| Subject: | Re: Bundling third-party libraries | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-42821@lists.php.net to get a copy of this message | ||
Pierre wrote:
On 6/7/06, Lukas Smith <lsmith@php.net> wrote:(Slightly offtopic, but found when I looked at the Console_ProgressBar). This package's page lists "No end-user documentation is available for this package." IMO without "end user documentation" code is not usable and it would be a good thing for PEAR to force documentation instead of some of the other rules... (I actually thought PEAR already mandated documentation?) regards, DerickSebastian Bergmann wrote:Arnaud Limbourg wrote:Which is what I did, for instance, with Console_Getopt by taking the PHP 4 code, rewriting it for PHP 5 + E_STRICT, and bundling it as PHPUnit2/Util/Getopt.php for PHPUnit 3. But this was only a short-term solution and it does not give me the means to implement featureBesides, even if the external package license should be changed the package maintainer can still use the old version and effectively fork the third-party library.requestslike colors and progress bars for the PHPUnit TextUI test runner, for example.We do have packages for progress bars and colors for console apps in PEAR. I am sure they are not E_STRICT compliant though.ProgressBar, for example, is E_STRICT compliant.