Re: fix to spaces in path

Greg Beaver 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 it - the new publicweb role which is proposed will not allow installation to "C:\Program Files\Apache Group", the default Apache location on windows. backwards compatibility issues: none - this patch is internal, and uses pre-programmed features of the same functions to do the job. API issues: none - no changes are visible to private or public functions, no other code need be changed. All in favor of fixing these bugs please +1, this will at least start the ball rolling. For those wishing to test or review this fix, I've attached the patch Greg

Let it be noted two things: 1) *nix can have spaces in directory names also, mkdir "My Documents" or mkdir My\ Documents should both work IME, this patch should allow *nix users who *do* put spaces in to use those directories for PEAR - its not *just* about Win32 (though, mostly it is) 2) Windows directories like "Program Files" can be shorted to the old 8.3 notation of "Progra~1" and "Apache~1", I wonder would PEAR allow these, did anyone check? I'll do it now. - Davey