Re: major issues with PEAR CVS

From: Date: Thu, 08 Apr 2004 14:23:10 +0000
Subject: Re: major issues with PEAR CVS
References: 1 2 3 4  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-245@lists.php.net to get a copy of this message
Hi Wez, This is correct, it is 3 lines long. The main issue with it not being cvs'ed is that there has been a bug in it for a few weeks/months that no one has been able to fix because it's not publicly accessible. It also requires Edin to do extra work if there is a bug, which doesn't seem fair somehow :) What would be best is to determine where the snapshots get go-pear.php from as well - is this grabbed from pearweb's public_html/go-pear in cvs, or from a pre-created go-pear.php on the snaps machine? Stefan's reminder about grabbing files from cvs is important, and the cvs move should involve a change in go-pear as well, as close to simultaneously as possible. Greg Wez Furlong wrote:
Right now it uses the same go-pear.bat that you see in current php5 snaps; everything else is fetched from pear.php.net or go-pear.org. We'd prefer to avoid accessing CVS if possible. go-pear.bat shouldn't be a problem though, since its just a couple of lines to launch go-pear.php, no?


« previous php.pear.core (#245) next »