Don't allow build paths in `~`
bcumming opened this issue · comments
The build tool rebinds ~ as a tmpfs in order to hide any user-specific Spack configuration that would be present in ~/.spack.
This causes the build step to fail if the build is being performed in a sub-directory of $HOME.
The solution is to check the path X provided in -b X, check that it is not a child of ~.
Would a simpler solution be to instead do something like export SPACK_USER_CONFIG_PATH=$(mktemp -d) (and maybe SPACK_USER_CACHE_PATH)? This way you wouldn't have any restrictions on where the build can happen.