"port install" fails on local portfile repository on a volume whose name contains a space

[rb@…]

I am developing a portfile using the guide at ​http://guide.macports.org/#development.local-repositories

My home directory is on a secondary volume whose name is "Silverbird HD" and so contains a space. "port install" does not protect its path names against spaces and fails. See below.

Note: Renaming my volume is a workaround, not a fix :)

rb@silverbird$ sudo port install mps
Password:
Error: Unable to execute port: /opt/local/var/macports/build/_Volumes_Silverbird: no such file or directory
rb@silverbird$ ls /opt/local/var/macports/build/
_Volumes_Silverbird HD_Local_Users_rb_ports_devel_mps
_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc47
_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm
_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_pandoc

[ryandesign (Ryan Carsten Schmidt)]

Using paths containing spaces is not supported, not just by MacPorts, but by most of the software you might want to install using MacPorts. Duplicate of #35910.

[rb@…]

I appreciate that, and I've read the other report carefully, and this isn't quite the same. You can decline to fix it, of course, but I think this is about the MacPorts software itself not quoting a path. I'm not attempting to install MacPorts or any software fetched with MacPorts on a path with a space in it.