diff options
author | David Alexander <techxdave@users.noreply.github.com> | 2023-06-26 14:38:14 -0600 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-06-26 13:38:14 -0700 |
commit | 66f75407d136c0c06ed01774d5815728afba35ca (patch) | |
tree | fec471c76e7dcc6f34697bce56acf58f667cb9a5 /var | |
parent | 5db241c755ecc95787aa2158af0af08ef7c34de0 (diff) | |
download | spack-66f75407d136c0c06ed01774d5815728afba35ca.tar.gz spack-66f75407d136c0c06ed01774d5815728afba35ca.tar.bz2 spack-66f75407d136c0c06ed01774d5815728afba35ca.tar.xz spack-66f75407d136c0c06ed01774d5815728afba35ca.zip |
Updates to symlinking for Windows (#34701)
* Support hardlinks/junctions on Windows systems without developer
mode enabled
* Generally, use of llnl.util.symlink.symlink is preferred over
os.symlink since it handles this automatically
* Generally an error is now reported if a user attempts to create a
symlink to a file that does not exist (this was previously allowed
on Linux/Mac).
* One exception to this: when Spack installs files from the source
into their final prefix, dangling symlinks are allowed (on
Linux/Mac - Windows does not allow this in any circumstance).
The intent behind this is to avoid generating failures for
installations on Linux/Mac that were succeeding before.
* Because Windows is strict about forbidding dangling symlinks,
`traverse_tree` has been updated to skip creating symlinks if they
would point to a file that is ignored. This check is not
transitive (i.e., a symlink to a symlink to an ignored file would
not be caught appropriately)
* Relocate function: resolve_link_target_relative_to_the_link
(this is not otherwise modified)
Co-authored-by: jamessmillie <smillie@txcorp.com>
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions