#21787 [Dup->Csd]: go-pear/installer using relative paths?
| From: | sniper@php.net | Date: | Thu, 22 May 2003 01:10:49 +0000 |
| Subject: | #21787 [Dup->Csd]: go-pear/installer using relative paths? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-16607@lists.php.net to get a copy of this message | ||
ID: 21787
Updated by: sniper@php.net
Reported By: danielc at analysisandsolutions dot com
-Status: Duplicate
+Status: Closed
Bug Type: PEAR related
Operating System: Windows NT 4.0
PHP Version: 4.3.2RC1
Previous Comments:
------------------------------------------------------------------------
[2003-05-21 20:10:39] sniper@php.net
Bug #21619 is closed, closing this too.
------------------------------------------------------------------------
[2003-03-27 11:24:18] danielc at analysisandsolutions dot com
Considering this is a verified bug and you're consolidating the
activity to a different bug report, the appropiate status is
"Duplicate."
------------------------------------------------------------------------
[2003-03-27 06:34:09] edink@php.net
Concetrating all PEAR@win32 install problems in #21619. Closing this
one.
------------------------------------------------------------------------
[2003-03-26 16:04:35] stone@php.net
verified with 4.3.2 RC1 on NT and XP PRO
------------------------------------------------------------------------
[2003-02-26 14:02:55] danielc at analysisandsolutions dot com
This definitely has to do with the TEMP and/or TMP environment
variable.
I've built a new system. Windows 2000. PHP 4.3.1. go-pear.php v
1.34.
The user TMP and TEMP variables are set to a directory on the D: drive.
Running go-pear.php similarly split the installation between the drive
I designated and the temp drive.
To further confirm this hypothesis, I removed the user environment
variables, leaving the system TMP and TEMP variables which lead to a
directory on the C: drive. Rerunning go-pear.php produced things going
to the right drive.
------------------------------------------------------------------------
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/21787
--
Edit this bug report at http://bugs.php.net/?id=21787&edit=1