Hi Folks:
Downloaded the latest snapshot, php5-win32-200401081130, and am enjoying
the new file layout.
Both the CGI and CLI exe's are now in the base directory. CLI is called
"php.exe" and the CGI is called "php-cgi.exe." Please consider reversing
the names. Making the CLI "php-cli.exe" and the CGI "php.exe" will make
installation less of a hastle.
Users and their computers expect the php.exe to be the CGI and are using
it to serve web pages. While having each user individually change their
files isn't insurmountable, it's an unnecessary step for many thousands of
people. And for some people, it's a step they'd need to repeat over and
over as they unzip new snapshots.
By the way, thanks for renaming the dll. I'm looking forward to running 4
and 5 concurrently as CGI's on my windows development system.
Thanks for your consideration,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
If you need to configure php5 separately from php4, you're going to be
editing your server config anyway, so (IMO at least) this is not an issue.
The CLI version should remain php.exe (this has been discussed before).
Consider the CGI name change a progressive one that will help avoid
confusion with CLI and CGI (which were both named php.exe). Now that
PHP is expanding outside of the role of a webserver only language,
more and more people will be using the CLI version of PHP especially
now that win32 PHP is much more attractive for admin tasks (COM!)
than it has been in previous releases.
The old style dir structure meant that you had to rename the CGI and
then move the CLI out of a sub-directory in order to be able to use
both CLI and CGI on the same box; clearly this is much more hassle
to do for every snap than to change your server config only once :-)
--Wez.
Both the CGI and CLI exe's are now in the base directory. CLI is called
"php.exe" and the CGI is called "php-cgi.exe." Please consider reversing
the names. Making the CLI "php-cli.exe" and the CGI "php.exe" will make
installation less of a hastle.Users and their computers expect the php.exe to be the CGI and are using
it to serve web pages. While having each user individually change their
files isn't insurmountable, it's an unnecessary step for many thousands
of
people. And for some people, it's a step they'd need to repeat over and
over as they unzip new snapshots.By the way, thanks for renaming the dll. I'm looking forward to running
4
and 5 concurrently as CGI's on my windows development system.
The old style dir structure meant that you had to rename the CGI and
then move the CLI out of a sub-directory in order to be able to use
both CLI and CGI on the same box;
Or don't change anything and just call the CLI using a the full path.
Pretty simple.
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
That doesn't work, since the php5*.dll is not found in the
same dir as the exe.
The old style dir structure meant that you had to rename the CGI and
then move the CLI out of a sub-directory in order to be able to use
both CLI and CGI on the same box;Or don't change anything and just call the CLI using a the full path.
Pretty simple.
That doesn't work, since the php5*.dll is not found in the
same dir as the exe.
Huh? What I've been doing...
To run CLI the script's pound bang is
#! c:/progra~1/php/cli/php
To run CGI the script's pound bang is
#! c:/progra~1/php/php
Worked just fine. Wouldnt be much different under the new file name
system, using different file names instead of different directory names.
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
And you have c:/program files/php dir in your path, right?
If you don't have it in your path, it won't work.
That doesn't work, since the php5*.dll is not found in the
same dir as the exe.Huh? What I've been doing...
To run CLI the script's pound bang is
#! c:/progra~1/php/cli/php
To run CGI the script's pound bang is
#! c:/progra~1/php/phpWorked just fine. Wouldnt be much different under the new file name
system, using different file names instead of different directory names.
And you have c:/program files/php dir in your path, right?
If you don't have it in your path, it won't work.
And a PHPRC environment variable set to that as well.
Don't know why this wasn't the default recommendation on installing PHP 4.
A documentation suggestion to this effect,
http://bugs.php.net/bug.php?id=24970, received no response. Whatever.
Thanks,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
While I dont care if the name changes for php5, I dont buy the premise
that more and more people will be using php outside the web. I think
cli has it's uses, but I think it will be a marginal group of people who
make large use of it.
Shane
Wez Furlong wrote:
If you need to configure php5 separately from php4, you're going to be
editing your server config anyway, so (IMO at least) this is not an issue.The CLI version should remain php.exe (this has been discussed before).
Consider the CGI name change a progressive one that will help avoid
confusion with CLI and CGI (which were both named php.exe). Now that
PHP is expanding outside of the role of a webserver only language,
more and more people will be using the CLI version of PHP especially
now that win32 PHP is much more attractive for admin tasks (COM!)
than it has been in previous releases.The old style dir structure meant that you had to rename the CGI and
then move the CLI out of a sub-directory in order to be able to use
both CLI and CGI on the same box; clearly this is much more hassle
to do for every snap than to change your server config only once :-)--Wez.
Both the CGI and CLI exe's are now in the base directory. CLI is called
"php.exe" and the CGI is called "php-cgi.exe." Please consider reversing
the names. Making the CLI "php-cli.exe" and the CGI "php.exe" will make
installation less of a hastle.Users and their computers expect the php.exe to be the CGI and are using
it to serve web pages. While having each user individually change their
files isn't insurmountable, it's an unnecessary step for many thousandsof
people. And for some people, it's a step they'd need to repeat over and
over as they unzip new snapshots.By the way, thanks for renaming the dll. I'm looking forward to running
4
and 5 concurrently as CGI's on my windows development system.
If you need to configure php5 separately from php4, you're going to be
editing your server config anyway, so (IMO at least) this is not an issue.
But why add needless steps? Let alone, I suspect the majority of users
don't play around with both 4 and 5 at the same time. It would be nice
for them to be able to kill/move 4 and drop 5 into it's place and have it
all run as expected.
Yes, I'm pedantic,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
Uh..we had this discussion back when CLI was introduced..
please don't start another useless thread about this.
It's fine as it is, move along.
--Jani
If you need to configure php5 separately from php4, you're going to be
editing your server config anyway, so (IMO at least) this is not an issue.But why add needless steps? Let alone, I suspect the majority of users
don't play around with both 4 and 5 at the same time. It would be nice
for them to be able to kill/move 4 and drop 5 into it's place and have it
all run as expected.Yes, I'm pedantic,
--Dan