runtime: `build.sh` fails when run in a directory that contains spaces
Running in such directory results in:
<path with a space>/runtime/eng/build.sh: line 156: <path with a space up to the space>: No such file or directory
It looks like this line is the cause: https://github.com/dotnet/runtime/blob/main/eng/build.sh#L156
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 22 (22 by maintainers)
There could be some weekly CI job that’d build and test from a directory that contains spaces and non-ASCII characters, this’d keep things working in check.
Sure, we all strive to avoid it, but some people are less lucky - in many institutions, universities, companies, IT may force a policy that requires people to use root folders with names beyond their control (e.g. based on their names that may contain a plethora of accent signs and spaces). While it’s a sad reality that today this doesn’t work, I think our north star should be ultimately making this fully functional, at the very least as a nod to our inclusiveness principle.