summaryrefslogtreecommitdiff
path: root/bin/spack.ps1
diff options
context:
space:
mode:
authorJohn W. Parent <45471568+johnwparent@users.noreply.github.com>2024-05-16 13:56:04 -0400
committerGitHub <noreply@github.com>2024-05-16 10:56:04 -0700
commit1ce09847d9ea15c1c0cc64a293f3011b66f2f520 (patch)
tree4cdaf79b65f1d1482c6bf00931ac61d3c27d048b /bin/spack.ps1
parent722d401394692413894e92eae3eb155eae2d80f2 (diff)
downloadspack-1ce09847d9ea15c1c0cc64a293f3011b66f2f520.tar.gz
spack-1ce09847d9ea15c1c0cc64a293f3011b66f2f520.tar.bz2
spack-1ce09847d9ea15c1c0cc64a293f3011b66f2f520.tar.xz
spack-1ce09847d9ea15c1c0cc64a293f3011b66f2f520.zip
Prefer llnl.util.symlink.readlink to os.readlink (#44126)
Symlinks on Windows can use longpath prefixes (\\?\); these are fine in the context of win32 API interactions but break numerous facets of Spack behavior that rely on string parsing/matching (archiving, binary distributions, tarball extraction, view regen, etc). Spack's internal readlink method (llnl.util.symlink.readlink) gracefully handles this by removing the prefix and otherwise behaving exactly as os.readlink does, so we should prefer that in all cases.
Diffstat (limited to 'bin/spack.ps1')
0 files changed, 0 insertions, 0 deletions