Re: Re: cvs: php-src /pear CODING_STANDARDS Makefile.frag PEAR.php README System.php catalog go-pear-list.php go-pear.bat install-pear.php
install-pear.txt package-Archive_Tar.xml package-Console_Getopt.xml package-PEAR.xml package.dtd template.spec /pear/Archive Tar.php
/pear/Archive/docs Tar.txt /pear/PEAR/Command Auth.php Build.php Common.php Config.php Install.php Mirror.php Package.php Registry.php Remote.php
/pear/PEAR/Frontend CLI.php /pear/docs Archive_Tar.txt rfc01_PEAR_pecl-binaries.txt rfc01_PEAR_subpackages.txt /pear/packages HTML_Template_IT-1.1.tar
Net_UserAgent_Detect-2.0.1.tar XML_RPC-1.3.1.tar /pear/scripts .cvsignore pear.bat pear.sh pearcmd.php pearwin.php
| From: | Klaus Guenther | Date: | Tue, 16 Aug 2005 09:30:39 +0000 |
| Subject: | Re: Re: cvs: php-src /pear CODING_STANDARDS Makefile.frag PEAR.php README System.php catalog go-pear-list.php go-pear.bat install-pear.php install-pear.txt package-Archive_Tar.xml package-Console_Getopt.xml package-PEAR.xml package.dtd template.spec /pear/Archive Tar.php /pear/Archive/docs Tar.txt /pear/PEAR/Command Auth.php Build.php Common.php Config.php Install.php Mirror.php Package.php Registry.php Remote.php /pear/PEAR/Frontend CLI.php /pear/docs Archive_Tar.txt rfc01_PEAR_pecl-binaries.txt rfc01_PEAR_subpackages.txt /pear/packages HTML_Template_IT-1.1.tar Net_UserAgent_Detect-2.0.1.tar XML_RPC-1.3.1.tar /pear/scripts .cvsignore pear.bat pear.sh pearcmd.php pearwin.php |
||
| References: | 1 2 3 4 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-3583@lists.php.net to get a copy of this message | ||
On 8/16/2005 11:48 AM, Tobias Schlitt spake the following words:
>Hi Klaus Guenther!
>On 08/16/05 11:04 you wrote:
>
>
>>It only applies to HEAD at the moment. So that means, it currently is
>>not planned to be bundled with PHP 6.
>>
>>
>
>Actually it's been bullshit anyway to keep the sources there, since
>they should reside under /pear-core instead.
>
>
You're right. If anything, the latest releases should always have been
pulled from /pear-core and not always manually synched.
Of course, that means that QA would need to keep on the ball 100% of the
time to prevent that maybe a broken version of the pear installer could
be bundled. That would be worse than pear not being there at all.
Klaus