Re: PEAR in PHP 4.3.0
| From: | Pierre-Alain Joye | Date: | Sat, 28 Sep 2002 22:21:12 +0000 |
| Subject: | Re: PEAR in PHP 4.3.0 | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-9666@lists.php.net to get a copy of this message | ||
On Sun, 29 Sep 2002 00:10:37 +0200
Markus Wolff <wolff@21st.de> wrote:
> I second each and every word. Using the windows registry is a bad
> thing and will create more complications that benefits.
Let me explain.
Using the registry on win XP/2K platform because this is the *only* way
to set permanent environment variables.
This is not and will not be the only way to configure PEAR on win32, but
a quick&easy way to do it. You cannot set environment variables in any
kind of autoexec.bat, or something like that, that does not work on
these platforms.
Setting them in the pear.bat will work only with the pear command
itself, but not with any others environments.
Using php.ini is not very good because this is (atm) a global setting
and cannot be personalized (IE a per host settings). ENV vars can be set
from most all http servers and per users in the registry. This will be
make possible to 'advanced' users to setup PEAR how they need, keeping
simplicity for all others.
The goals is not to fill the registry of tousands of value, people are
are always afraid as soon as someone says 'I would like to put it in
the registry' :-). We have to realize that is the way M$ chooses to
create Application datas for a user context or a global context, as
*unices did with rcX.local or other systemsV boot sequences.
How about a simple :
php-cli setuppear.php
... answering short question ...
double-click on PEAR.REG file and the wrost rookie user got a working
PEAR installation, is it not the way of simplicity ?
hth
pa