On Thu, 28 Feb 2002, Edin Kadribasic wrote: > Hello all, > > One of the new things in 4.2.0 will be CLI SAPI and modifications of the > build process that were made to make simultanious build with other SAPIs > possible. There are few issues that remain: > > 1. If you compile CGI binary and then issue 'make install' it will be > installed in $PREFIX/bin, then CLI will be put in the same place overwriting > it. Any suggestions on what to do in this situation?
Disable the cli when compiling the CGI sapi? Add a --install-cli-dir directive to configure? > > 2. php.ini search path has CWD as the first element. This is IMHO major > inconvinience if we want to make PHP more suitable for writing general > purpose applications like PHP-GTK, etc. The execution of the program shold > not depend on where the program was started from. Agreed, but as somebody pointed out earlier, some hosts use this feature to give customers their own php.ini. which should continue to work. > 3. Should CLI get its own php.ini? Some people have suggested php-cli.ini. > Others wanted Apache style <IfModule>... arguing that the two would be > mostly identical. I'd go with the <IfMOdule> thingy. I looked into the parser for this and it should be possible to add this functionality. Derick -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
