From: MinGW M. D. L. <NOH...@sp...> - 2007-03-16 09:11:42
|
I have been experimenting with portmaker for some time now, and have run into a few problems. Most of them concern the lack of quoting around variables and parameters. My Windows username is my real first, middle and lastname, including spaces. That proved to be a big problem for portmaker (and for configure-scripts, and for makefiles). I tried to fix the problem in portmaker by changing a lot of $1 into "$1", but that only exposed the same problem with configure/makefile. For now I resorted to set HOME in msys.bat and point it to a directory with no spaces in the name. I don't want to save the world in one go, so I will forget about the problem that the auto-tools has with spaces in directory names and concentrate on portmaker. Basically I want to know if the portmaker maintainers are interested in receiving patches for this problem, before I start to go through the scripts and add d-quotes a lot of places. -- Jan |
From: Greg C. <chi...@co...> - 2007-03-16 13:25:24
|
[Mail from "MinGW MSYS Discussion List" might be mistaken for a message from the mailing-list software or an official announcement; please consider changing your alias.] On 2007-3-16 9:11 UTC, MinGW MSYS Discussion List wrote: > > My Windows username is my real first, middle and lastname, including > spaces. That proved to be a big problem for portmaker (and for > configure-scripts, and for makefiles). > > I tried to fix the problem in portmaker by changing a lot of $1 into > "$1", but that only exposed the same problem with configure/makefile. Like many *nix tools, 'make' uses the space character as a delimiter, but ms windows encourages spaces in pathnames. Quoting may work around some of the conflicts, but not all. The 'make' mailing list archives, accessible here: http://savannah.gnu.org/mail/?group=make contain much discussion of this conflict. > For now I resorted to set HOME in msys.bat and point it to a directory > with no spaces in the name. That's generally the best solution. Another way is to use "8.3" filenames like "DOCUME~1\ADMINI~1", but hardcoding those is dangerous and generating them on the fly seems laborious. Maybe filesystem mounts would be yet another solution. > I don't want to save the world in one go, so I will forget about the > problem that the auto-tools has with spaces in directory names and > concentrate on portmaker. You've got scripts that use autotools, which use 'make', and you're thinking of changing the scripts to quote parameters, right? But will it be feasible to change the downstream tools so that they do the right thing with those quoted parameters? I'd consider that before embarking on this course. AFAIK, others have looked at those downstream problems and concluded that solving them isn't worth the cost when your "HOME" idea above sidesteps the issues neatly. |
From: Keith M. <kei...@us...> - 2007-03-17 23:29:07
|
On Friday 16 March 2007 09:11, MinGW MSYS Discussion List wrote: > Basically I want to know if the portmaker maintainers are interested > in receiving patches Patches are always welcome :-) However, you may wish to reconsider whether this particular effort will be worthwhile, in view of Greg Chicares' response, (which offers a well balanced perspective, and with which I completely agree). Working around the problem you percieve in portmaker may create only a tiny chip in the tip of the iceberg; avoiding spaces in path names in the first place seems the more favourable solution. Regards, Keith. |