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:36:59 +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 5 6 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-3586@lists.php.net to get a copy of this message | ||
On 8/16/2005 11:35 AM, Tobias Schlitt spake the following words:
> Hi Klaus Guenther!
> On 08/16/05 11:30 you wrote:
>
>
>>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.
>
>
> For 1.3 we'd keep the current way. For 1.4 I imagine that go-pear only
> provides a PHAR archive. Since this should always be stable, the latest
> can simple be pulled by the PHP packagers and be integrated.
>
> That would allow us to maintain a stable version in a unique place.
Yes. Let's wait for the dust to settle and then we can have an informed
(and civil) discussion on what solutions are possible. Right now, the
phar solution sounds very good to me.
Klaus