Re: config.w32.h...registry configuration
| From: | Daniel Beulshausen | Date: | Wed, 01 May 2002 19:11:30 +0000 |
| Subject: | Re: config.w32.h...registry configuration | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-83571@lists.php.net to get a copy of this message | ||
At 11:41 01.05.2002 -0700, Shane Caraveo wrote:
Daniel Beulshausen wrote:one could use the version string as a subkey, this would enable you to use different php.inis for different versions. daniel /*-- Daniel Beulshausen - daniel@php4win.com Using PHP on Windows? http://www.php4win.comAt 11:19 01.05.2002 -0700, Shane Caraveo wrote:they should be changed to use the windows registry anyway...Well, the specific example I saw was the extension dir, which is an ini setting. I would argue that pear_installdir could also be an ini setting. bindir does need some solution outside the ini file, maybe, but I think there could be some way to work around that. The reason I am *kind of* arguing against using the registry for these is due to having multiple installations of PHP. I currently have 6, 5 installs and my compiled version, so that I can test things. Dealing with php.ini in that situation is bad enough, adding registry configuration on top of that will make it even a bigger pain.i'm not talking about the per directory stuff, these are mostly non php.ini settings. things like PEAR_INSTALLDIR, PHP_BINDIR etc should be stored in the registry IMO. danielIt's already done, been there for a long time. php.ini values are configurable via registry, and can be done on a per-domain basis. It is kind of a pain to deal with configuration that way though.Feel free to do it :)this isn't going to be a big task, i'll put it onto my todo.