Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15723 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15783 invoked by uid 1010); 1 Apr 2005 22:09:03 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 15524 invoked from network); 1 Apr 2005 22:08:54 -0000 Received: from unknown (HELO pb1.pair.com) (127.0.0.1) by localhost with SMTP; 1 Apr 2005 22:08:54 -0000 X-Host-Fingerprint: 69.64.38.41 bluga.net Linux 2.5 (sometimes 2.4) (4) Received: from ([69.64.38.41:45553] helo=bluga.net) by pb1.pair.com (ecelerity HEAD r(5268)) with SMTP id D7/96-22409-336CD424 for ; Fri, 01 Apr 2005 17:07:48 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by bluga.net (Postfix) with ESMTP id 8F47921C6B7; Fri, 1 Apr 2005 16:05:19 -0600 (CST) Received: from bluga.net ([127.0.0.1]) by localhost (bluga.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21139-09; Fri, 1 Apr 2005 16:05:19 -0600 (CST) Received: from [192.168.0.102] (cpe-66-65-39-8.nyc.res.rr.com [66.65.39.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bluga.net (Postfix) with ESMTP id 3308C21C1EC; Fri, 1 Apr 2005 16:05:19 -0600 (CST) Message-ID: <424DC61C.5050900@php.net> Date: Fri, 01 Apr 2005 17:07:24 -0500 User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Zeev Suraski Cc: internals@lists.php.net References: <5.1.0.14.2.20050401235721.0668c050@localhost> In-Reply-To: <5.1.0.14.2.20050401235721.0668c050@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at bluga.net Subject: Re: PHP 5.0.4 PEAR issue From: cellog@php.net (Greg Beaver) Zeev Suraski wrote: > Folks, > > We have a bit of a situation with the PEAR distro that's embedded in > 5.0.4. It's missing the RunTest.php file, so PEAR doesn't install. > > The options we have, as far as I can tell, are: > > [a] Re-release 5.0.4 with that file > [b] Release 5.0.5 with that file (seems a bit too aggressive considering > there are no code changes, and may cause confusion) > [c] Instruct people to install PEAR from http://go-pear.org > > I lean towards option [a]. Thoughts? I think [a] is the best choice as well, perhaps with a brief note at php.net? This is my fault and is no April Fool's joke. The problem was that RunTest.php was sitting in my local checkout but was not properly cvs added, so my install tests worked just fine. This has been corrected. To avoid this for the future, I'm brainstorming ideas for a script that can be used to sync with released PEAR packages so that pear can be removed from php-src altogether in CVS, and simply synced as part of a cron job for the snaps machines. Any advice or admonitions would be appreciated. Greg Pierre: can we work on this in tandem?