RE: [PEAR-DEV] PEAR in PHP 4.3.0
| From: | Urs Gehrig | Date: | Sat, 28 Sep 2002 17:35:52 +0000 |
| Subject: | RE: [PEAR-DEV] PEAR in PHP 4.3.0 | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-9656@lists.php.net to get a copy of this message | ||
> > This solution solve the pear/php path, but, imho, I do not like
> to see hard coded default path, this is always sources of
... in that case, we should get rid of definitions like those in
config.w32.h.in:
/* Default PHP / PEAR directories */
#define CONFIGURATION_FILE_PATH "php.ini"
#define PHP_BINDIR "c:\\php4"
#define PHP_PREFIX "c:\\php4"
#define PHP_CONFIG_FILE_PATH
(getenv("SystemRoot"))?getenv("SystemRoot"):""
#define PHP_DATADIR "c:\\php4"
#define PHP_EXTENSION_DIR "c:\\php4"
#define PHP_INCLUDE_PATH ".;c:\\php4\\pear"
#define PHP_LIBDIR "c:\\php4"
#define PHP_LOCALSTATEDIR "c:\\php4"
#define PHP_SYSCONFDIR "c:\\php4"
#define PEAR_INSTALLDIR "c:\\php4\\pear"
... and let the pear administrator configure its settings at
the installation stage of pear (e.g. while running go-pear).
> problems :-). A clean and 'easy to configure' way is the use of
> REG file on windows 2k/XP and certainly for win98/SE/ME. A reg
> file provides a fast and customisable (from a make, go-pear, php
> scripts, or manually) system to set permanent environment vars.
> > Theses env vars should the usual we can set using go-pear. The
> main problem on win32 platform is most of users just download the
> zip archive and uncompress it under their folder. A simple README
> for both PHP & PEAR telling how to set up the needed env vars
... if we could build go-pear in a way, that one has to configure
those env vars at first run before ever having any pear package
installed, that could help to motivate them to read that README ;)
-urs