On Tuesday 03 August 2004 14:51, Wez Furlong wrote:
> Thou shalt not put application data into SYSTEMROOT.
> Don't do it. Ever.
> Really!
>
> Read the M$ guidelines on this stuff, including the dll-hell articles
> and the setup and install guidelines. Read the documentation on .ini
> files and the registry.
>
> They've all been telling developers to keep their crap out of the
> system folders; they don't belong there.
>
> Do *NOT* tell our newbie users to put stuff in there, because they
> invariably screw things up during installation, uninstallation and
> upgrade time. It's a big headache. Let's not go there.
According to what you said I expect changes to
main/config.w32 .h and win32/build/config.w32.h.in to _not_ make use of
#define PHP_CONFIG_FILE_PATH (getenv("SystemRoot"))?getenv("SystemRoot"):""
for default path/directories
Instead it should use something like "c:\\php5" or "c:\\php4 as default
location.
Changing this would have the benefit, that we could instruct people to use the
default location c:\php4 or c:\php5 and they do not need to use PATH or
PHPRC, right?
This sort of installation is also used by MySQL on Win:
Unzip all contents to the default location, copy php.ini-* to php.ini and you
are done. This way php is self-contained in a daefault location without any
modifications.
If one wants to put php in a different location than c:\php[45] (not suitable
for newbie users) they can use PATH, PHPRC etc.
Hope, I got this right, or I am missing something important?
Friedhelm
> On Mon, 2 Aug 2004 20:54:15 +0200, Friedhelm Betz <[EMAIL PROTECTED]> wrote:
> > I thought about twice and I wonder why it is preferable to use PHPRC
> > instead just copy php-(sapiname).ini to SYSTEMROOT?
> >
> > Using PHPRC is indeed nice but seems to be a superfluous hurdle for
> > newbies. We do not talk about 'copy dlls' just one/two ini-files to
> > SYSTEMROOT. Nothing wrong with that, IMHO.
--
http://www.jungle-world.com/
