#21787 [Opn]: go-pear/installer using relative paths?
| From: | danielc at analysisandsolutions dot com | Date: | Wed, 26 Feb 2003 20:02:56 +0000 |
| Subject: | #21787 [Opn]: go-pear/installer using relative paths? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-13942@lists.php.net to get a copy of this message | ||
ID: 21787
User updated by: danielc at analysisandsolutions dot com
Reported By: danielc at analysisandsolutions dot com
Status: Open
Bug Type: PEAR related
Operating System: Windows NT 4.0
PHP Version: 4.3.0
New Comment:
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.
Previous Comments:
------------------------------------------------------------------------
[2003-01-20 19:23:37] danielc at analysisandsolutions dot com
Hi:
Installing PEAR via go-pear winds up splitting the installation between
two drives. It seems the installer program specifies a relative path
rather than a full path.
Here's what I did.
f:cli\php -n -r "include 'http://go-pear.org';"
I go along with all of the defaults.
I wind up getting two php4\pear directories. One is c:\php4\pear,
which has the full .registry directory plus three blank directories:
data, docs, tests. The second is g:\php4\pear, which contains the main
files, such as Db.php, Mail.php, etc.
I suspect the installation has wound up there because my TEMP dir is on
the G drive.
I've tried several incantations, but all wind up doing basically the
same thing...
Thanks,
--Dan
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=21787&edit=1