Re: [PHP-DEV] Always building command line PHP

2002-01-03 Thread Jon Parise
On Thu, Jan 03, 2002 at 09:37:38PM +, [EMAIL PROTECTED] wrote: > > It should still be possible to build a separate CGI executable with a > > different php.ini path for those sites that require it. > > Don't get too stuck on the idea that PHP at the command line is only > for CGI. In fact I

Re: [PHP-DEV] Always building command line PHP

2002-01-03 Thread php4
** Reply to note from Jon Parise <[EMAIL PROTECTED]> Thu, 3 Jan 2002 16:39:20 -0500 > > I agree that it's sometimes necessary to have different configuration > files, but I don't consider it a necessity. I do. > It should still be possible to build a separate CGI executable with a > differen

Re: [PHP-DEV] Always building command line PHP

2002-01-03 Thread php4
Addressed to: [EMAIL PROTECTED] [EMAIL PROTECTED] ** Reply to note from J Smith <[EMAIL PROTECTED]> Thu, 03 Jan 2002 16:26:38 -0500 > I would prefer separate php.ini files, maybe something like > php-cli.ini for the default CLI file and and php.ini for the > Apache/web server mod

Re: [PHP-DEV] Always building command line PHP

2002-01-03 Thread php4
** Reply to note from Jon Parise <[EMAIL PROTECTED]> Thu, 3 Jan 2002 15:36:32 -0500 > > On Wed, Jan 02, 2002 at 04:39:24PM +, [EMAIL PROTECTED] > wrote: > > > One thing to consider, at least the php.ini location needs to be > > different between the module and command line compiles. I s

Re: [PHP-DEV] Always building command line PHP

2002-01-03 Thread Andi Gutmans
At 04:39 PM 1/3/2002 -0500, Jon Parise wrote: >On Thu, Jan 03, 2002 at 04:26:38PM -0500, J Smith wrote: > > > Just a little annoyance I guess. Nothing to get in knots over. But in the > > end, I would prefer separate php.ini files, maybe something like > > php-cli.ini for the default CLI file and

Re: [PHP-DEV] Always building command line PHP

2002-01-03 Thread Jon Parise
On Thu, Jan 03, 2002 at 04:26:38PM -0500, J Smith wrote: > Just a little annoyance I guess. Nothing to get in knots over. But in the > end, I would prefer separate php.ini files, maybe something like > php-cli.ini for the default CLI file and and php.ini for the Apache/web > server module defa

Re: [PHP-DEV] Always building command line PHP

2002-01-03 Thread J Smith
Actually, I wouldn't mind having seperate php.ini files for the web server module and for the CLI executeable, either. Here's what happened to me recently -- I had upgraded my servers from 4.1.0 (one of the release candidates, I've been following PHP development rather closely) to 4.1.0 final

Re: [PHP-DEV] Always building command line PHP

2002-01-03 Thread Jon Parise
On Wed, Jan 02, 2002 at 04:39:24PM +, [EMAIL PROTECTED] wrote: > One thing to consider, at least the php.ini location needs to be > different between the module and command line compiles. I suspect most > people will have quite a few other differences in ./configure options > between them to

Re: [PHP-DEV] Always building command line PHP

2002-01-02 Thread php4
** Reply to note from Jon Parise <[EMAIL PROTECTED]> Wed, 2 Jan 2002 15:32:58 -0500 > > On Wed, Jan 02, 2002 at 09:33:32PM +0200, Andi Gutmans wrote: > > > Creating a CLI sapi module w/o all of the CGI crap is extremely easy. > > What might be more challenging is fixing the build so that it

[PHP-DEV] Always building command line PHP

2002-01-02 Thread Jon Parise
On Wed, Jan 02, 2002 at 09:33:32PM +0200, Andi Gutmans wrote: > Creating a CLI sapi module w/o all of the CGI crap is extremely easy. > What might be more challenging is fixing the build so that it always builds > the cli. I think this should be considered a high priority. The PEAR tools requi