On Sun, 15 Dec 2002, John Coggeshall wrote:
> >I see that renaming the CGI to php-cgi might break things indeed, and
> >that's never a good idea. But so is changing the name of the CLI (php)
> >to something else. It also breaks things, not only for me, but
> >also for
> >countless others using
On Sun, 15 Dec 2002, Sebastian Nohn wrote:
> Why do we need new releases every couple of weeks? Don't misunderstand me, I
> would really like to see 4.3 released, as this is the first version since
> around one year that will have only a few bugs on Tru64, on the other hand
> I'm really shocked, h
> -Original Message-
> From: Derick Rethans [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, December 15, 2002 7:21 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; 'Stig S. Bakken'; 'Sterling Hughes'; 'Andrei
> Zmievski'; [EMAIL PROTECTED]
&g
On Sun, 15 Dec 2002, Marcus Börger wrote:
> At 18:33 15.12.2002, John Coggeshall wrote:
> > >I see that renaming the CGI to php-cgi might break things indeed, and
> > >that's never a good idea. But so is changing the name of the CLI (php)
> > >to something else. It also breaks things, not only for
At 18:33 15.12.2002, John Coggeshall wrote:
>I see that renaming the CGI to php-cgi might break things indeed, and
>that's never a good idea. But so is changing the name of the CLI (php)
>to something else. It also breaks things, not only for me, but
>also for
>countless others using the CLI with
> >I see that renaming the CGI to php-cgi might break things indeed, and
> >that's never a good idea. But so is changing the name of the CLI (php)
> >to something else. It also breaks things, not only for me, but
> >also for
> >countless others using the CLI with the name 'php'. We also need to
>I see that renaming the CGI to php-cgi might break things indeed, and
>that's never a good idea. But so is changing the name of the CLI (php)
>to something else. It also breaks things, not only for me, but
>also for
>countless others using the CLI with the name 'php'. We also need to
>think a
On Sun, 15 Dec 2002, Zeev Suraski wrote:
> At 15:48 15/12/2002, Derick Rethans wrote:
> >I see that renaming the CGI to php-cgi might break things indeed, and
> >that's never a good idea. But so is changing the name of the CLI (php)
> >to something else. It also breaks things, not only for me, but
At 15:48 15/12/2002, Derick Rethans wrote:
I see that renaming the CGI to php-cgi might break things indeed, and
that's never a good idea. But so is changing the name of the CLI (php)
to something else. It also breaks things, not only for me, but also for
countless others using the CLI with the na
On Sun, 15 Dec 2002, Stig S. Bakken wrote:
> > This will break the idea of having 'php' (the CLI) on as much systems as
> > possible (for PEAR). It seems that integrating the two (CGI and CLI)
> > _seems_ like the best solution, although I do not favor this due to
> > technical reasons.
>
> Fo
On Thu, 12 Dec 2002, Derick Rethans wrote:
> On Thu, 12 Dec 2002, Sterling Hughes wrote:
>
> > > How about we simply add a configure option to control this?
> > >
> > > --enable-simple-cli-name would build CGI as php-cgi and CLI as php
> > >
> > > That way we preserve BC and let those who like
On Thu, 12 Dec 2002, Sterling Hughes wrote:
> > How about we simply add a configure option to control this?
> >
> > --enable-simple-cli-name would build CGI as php-cgi and CLI as php
> >
> > That way we preserve BC and let those who like CLI named 'php' have that
> > too.
This will break the id
> How about we simply add a configure option to control this?
>
> --enable-simple-cli-name would build CGI as php-cgi and CLI as php
>
> That way we preserve BC and let those who like CLI named 'php' have that
> too.
>
you mean instead of ::
# mv php-cli php
?
-Sterling
--
PHP Development M
13 matches
Mail list logo
