ID: 19712
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Closed
Bug Type: Compile Failure
Operating System: Any
PHP Version: 4.2.1
New Comment:
Trying to support spaces in path names opens up a can of worms without
any real benefit.
If your administrator has made the mistake to give you a home directory
beneath such a path, complain to him/her. It is very likely that the
person is simply inexperienced.
Previous Comments:
------------------------------------------------------------------------
[2002-10-02 07:41:12] [EMAIL PROTECTED]
I don't think so...
Perhaps "blanks in dirnames are a no-no for developers", but why one
should do exotic things like:
$cp /usr/local/bin/phpize /home/user/my_ext/phpize
$cd /home/user/my_ext
$vi phpize
...
$./phpize
Is it possible that one have no control over upper level dirs? I think
nothing should not be done in one and only one situation: the patch
will have some negative side effects. In the case I don't see ones.
------------------------------------------------------------------------
[2002-10-02 07:14:36] [EMAIL PROTECTED]
why do you do that?
even if we fix this -> blanks in dirnames are a no-no for developers
this fires back in lots of places (e.g. find ... | xargs ... )
so it is an absolute bad idea in the first place ...
------------------------------------------------------------------------
[2002-10-02 06:52:40] [EMAIL PROTECTED]
changing category
------------------------------------------------------------------------
[2002-10-02 06:51:25] [EMAIL PROTECTED]
$mkdir "My Directory"
$cd "My Directory"
$touch config.m4
$phpize
usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target
cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory
usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target
cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory
mv: build/rules_pear.mk: No such file or directory
The problem is here:
(cd $phpdir && cp $FILES_BUILD $builddir/build)
(cd $phpdir && cp $FILES $builddir)
We consider that one should use "${phpdir}" and "${builddir}" to
eliminate the problem.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=19712&edit=1