Since we are not going to support base paths containing
spaces in the build system, I fail to see the point of this
patch. Thus, I consider #28847 to be bogus.
- Sascha
On Sat, 19 Jun 2004, Jan Lehnardt wrote:
> jan Sat Jun 19 15:39:56 2004 EDT
>
> Modified files:
> /php-src/scripts phpize.in
> Log:
> - phpize now can handle directories with spaces in their name (#28847)
>
>
> http://cvs.php.net/diff.php/php-src/scripts/phpize.in?r1=1.13&r2=1.14&ty=u
> Index: php-src/scripts/phpize.in
> diff -u php-src/scripts/phpize.in:1.13 php-src/scripts/phpize.in:1.14
> --- php-src/scripts/phpize.in:1.13 Sat Jan 3 09:03:46 2004
> +++ php-src/scripts/phpize.in Sat Jun 19 15:39:56 2004
> @@ -75,9 +75,9 @@
>
> phpize_check_shtool()
> {
> - test -x $builddir/build/shtool || chmod +x $builddir/build/shtool
> + test -x "$builddir/build/shtool" || chmod +x "$builddir/build/shtool"
>
> - if test ! -x $builddir/build/shtool; then
> + if test ! -x "$builddir/build/shtool"; then
> phpize_no_shtool
> exit 1
> fi
> @@ -88,15 +88,15 @@
> {
> test -d build || mkdir build
>
> - (cd $phpdir && cp $FILES_BUILD "$builddir"/build)
> - (cd $phpdir && cp $FILES "$builddir")
> + (cd "$phpdir" && cp $FILES_BUILD "$builddir/build")
> + (cd "$phpdir" && cp $FILES "$builddir")
> }
>
> phpize_replace_prefix()
> {
> sed \
> -e "[EMAIL PROTECTED]@#$prefix#" \
> - < $phpdir/phpize.m4 > configure.in
> + < "$phpdir/phpize.m4" > configure.in
> }
>
> phpize_autotools()
>
> --
> PHP CVS Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
