Re: fix to spaces in path
| From: | Stan Lemon | Date: | Sun, 03 Aug 2003 03:29:50 +0000 |
| Subject: | Re: fix to spaces in path | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-19162@lists.php.net to get a copy of this message | ||
It seems foolish to call programming that isn't cross platform, and yet is intended to be, a "problem" and not a "bug". Now, you may be looking at it from a strictly *nix perspective, and fine I can respect that. But to exclude Windows users from defining exactly where they place something sounds to me like a bug.
Also I think you'll notice that Greg, in his unlimited wisdom and open mindness has not compromised anything for any other platform, he' simply made a correction in an area which formerly excluded a platform.
Call it what you wish, but the patch is still a necessity and it would be silly to not include it.
- Stan
Pierre-Alain Joye wrote:
On Sat, 02 Aug 2003 14:27:59 -0400 Greg Beaver <greg@chiaraquartet.net> wrote:This is your gadfly speaking. I'd like to commit the patch that fixes the spaces in path issue. Perhaps a show of hands in favor of fixing this problem would help move things along? Here is a list of the problems with spaces in paths that are solved by this fix: - pear install to a subdirectory of "C:\Program Files" will not work. "C:\Program Files" is the most commonly used install directory on windows- pear package will not work in any subdirectory containing spaces, and will create and possibly overwrite folders of the same name as the suffix. So if you have 2 directories "C:\Web" and C:\Web Pages", the pear package command will overwrite the contents of C:\Web and fail with a cryptic error message about not being able to copy a random file with .tmp pre-pended to itThis is not actually not a bug as I said. However if this patch solves this "problem" and allow win32 users to use their "damned" bad pathnames, well, we should apply it. Before that, We have to check it and be sure it does not break anything around and works well on any platform (with spaces or not). If spaces do not work well on other platform, we'll run in troubles with this patch. I would not like to break other platform to allow win32 users the use of non portable pathnames.All in favor of fixing these bugs please +1, this will at least start the ball rolling.Patch does not need a poll to be applied or not. This is up to the maintainers to decide. As anything else related to a specific package. thanks for your work :) pierre