summaryrefslogtreecommitdiff
path: root/bin/spack-tmpconfig
diff options
context:
space:
mode:
authorHarmen Stoppels <harmenstoppels@gmail.com>2023-02-20 19:14:27 +0100
committerGitHub <noreply@github.com>2023-02-20 19:14:27 +0100
commitc1ff7bbf04a27f483770c4351e662d7fa8f76686 (patch)
treef6d9aacd768756fa24a56e8f4321d1ab20cff78c /bin/spack-tmpconfig
parentaa708c89812711caaecb4033e2a66c98128a9d5a (diff)
downloadspack-c1ff7bbf04a27f483770c4351e662d7fa8f76686.tar.gz
spack-c1ff7bbf04a27f483770c4351e662d7fa8f76686.tar.bz2
spack-c1ff7bbf04a27f483770c4351e662d7fa8f76686.tar.xz
spack-c1ff7bbf04a27f483770c4351e662d7fa8f76686.zip
environment views: better, earlier error on clash (#35541)
Spack generally ignores file-file projection clashes in environment views, but would eventually error when linking the `.spack` directory for two specs of the same package. This leads to obscure errors where users have no clue what the issue is and how to fix it. On top of that, the error comes very late, since it happens when the .spack dir contents are linked (which happens after everything else) This PR improves that by doing a quick check ahead of time if clashes are going to be anticipated (by simply checking for clashes in the projection of each spec's .spack metadir). If there are clashes, a human-readable error is thrown which shows two of the conflicting specs, and tells users to user unify:true, view:false, or set up custom projections.
Diffstat (limited to 'bin/spack-tmpconfig')
0 files changed, 0 insertions, 0 deletions