#21619 [Com]: go-pear fails to install "pear/scripts" directory

ID: 21619 Comment by: alan at akbkhome dot com Reported By: michele dot manzato at verona dot miz dot it Status: Critical Bug Type: PEAR related Operating System: Win32 PHP Version: 4.3.2Rc1 New Comment: Workaround. ignore the comment about pearwin.php - it's an old file? put this in the php4 directory http://cvs.php.net/co.php/php4/pear/scripts/pear.in?login=2&r=1.67 modify the pear.bat to point to it. modify the pear.in file and change the @include_path@ etc. to the correct locations. Previous Comments: ------------------------------------------------------------------------ [2003-03-21 22:18:10] alan at akbkhome dot com workaround download http://cvs.php.net/co.php/php4/pear/scripts/pearwin.php?login=2&r=1.10 put it in the php4 directory and modify the pear.bat script (in wordpad - save as dos file) to point to it. ------------------------------------------------------------------------ [2003-03-21 22:16:43] alan_k@php.net confirmed - this is release critical for pear. totaly clean install: cd C:/php4 go-pear .... start process - gets to installing packages.. .. stops failing to make directory c://php4// (something) go-pear (again) goes all the way through. - failed to install pearwin.php - pear.bat has unix line breaks - rendering it impossible to run ------------------------------------------------------------------------ [2003-03-19 13:14:19] jacobhanson at firsthealth dot com Verified same behaviour on WinXP SP1 w/4.3.2rc1. :[ ------------------------------------------------------------------------ [2003-03-18 09:48:11] T dot Haas at Xardal dot de I Work with Windows 2000. My pear.bat can't find some pathes and doesn't work too. I guess my problem is the same problem as noticed. ------------------------------------------------------------------------ [2003-03-14 10:05:47] christian at nospam dot spam problem still exists in 4.3.1 and 4.3.2RC1 under Windows. :-( ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/21619 -- Edit this bug report at http://bugs.php.net/?id=21619&edit=1