ID: 24075
Updated by: [EMAIL PROTECTED]
Reported By: Sven dot Schnitzke at t-online dot de
-Status: Open
+Status: Closed
Bug Type: Feature/Change Request
Operating System: WIN98SE
PHP Version: 4.3.2
New Comment:
The manual installation instructions have been updated to _don't_
advise to copy the files to the windows dir.
Previous Comments:
------------------------------------------------------------------------
[2003-06-10 07:59:38] [EMAIL PROTECTED]
fine, let's make this a feature request.
------------------------------------------------------------------------
[2003-06-10 03:44:27] Sven dot Schnitzke at t-online dot de
Before we start flaming (_real_ OS, ...) I would like to turn your
attention to the first sentence of my message.
I will happily be settling with calling it a feature request:
Please base relative path specs for extension dir on the
folder the executable resides in (and re-think the decision
of packing php-cli into another folder, btw. what's the rationale
behind that?).
There are bulks of user comments and recommendations to put all the
dlls into WINSYS folder which is a _very_ bad startegy when it comes to
upgrading. And it is caused by
this feature.
IMHO program extensions do by all means belong to the program and not
to the data (in the sense that for PHP
scripts are data).
Second: (Just curious) I use Apache with mod_php. How do you get any
relevant information on this config out of calling PHP.EXE?
Last: Using a PIF to start PHP comes from 2 points: I use the pif to
customize the command window and to set the current folder so PHP
starts in a defined environment.
I don't believe anything discussed around this issue has
anything to do with the _flavor_ of WIN (98SE is not the only one I use
- it just happens to be the one on the machine I first loaded PHP 4.3.2
on)
------------------------------------------------------------------------
[2003-06-10 03:04:01] [EMAIL PROTECTED]
Can't see any bug here..
------------------------------------------------------------------------
[2003-06-10 02:38:12] [EMAIL PROTECTED]
<Sorry, the problem was in go-pear.php. It tries to invoke
php.exe -v to learn something of the returned string. With
my inst the cli version of php is supposed to be invoked via
PIF and cannot be launched directly via exec. It was this
'inner' call that issued the complaints about the missing
dlls.>
It tries to detect the current SAPI. Why do you use a pif do launch
php? Then I do not know what is related with PEAR if php launched with
a pif does not find some dlls. Comments?
btw, have you think about moving to real OS? like something newer than
win98se? win2K?
pierre
------------------------------------------------------------------------
[2003-06-09 08:18:15] [EMAIL PROTECTED]
I've no idea what PHP 4.4-dev is..last release is 4.3.2..
Reclassified as pear bug.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/24075
--
Edit this bug report at http://bugs.php.net/?id=24075&edit=1
