Steps to reproduce
I find it surprising that symlink falls back to a copy on Windows, and in some cases it is just bad. In particular here:
|
symlink(new_root, tmp_symlink_name) |
The trick is to update views atomically, effectively
ln -s new_dir ._view_link
mv ._view_link view
Can symlink just remain a symlink instead of something hard to reason about?
Error message
No response
Information on your system
.
General information
Steps to reproduce
I find it surprising that
symlinkfalls back to a copy on Windows, and in some cases it is just bad. In particular here:spack/lib/spack/spack/environment/environment.py
Line 535 in 6611f0b
The trick is to update views atomically, effectively
Can symlink just remain a symlink instead of something hard to reason about?
Error message
No response
Information on your system
.
General information
spack debug reportand reported the version of Spack/Python/Platform