diff options
author | Greg Becker <becker33@llnl.gov> | 2020-07-09 13:08:51 -0500 |
---|---|---|
committer | Peter Scheibel <scheibel1@llnl.gov> | 2020-07-10 13:05:49 -0700 |
commit | afbb4a5cbade91d0b80e39ecbd98051bb8fd7628 (patch) | |
tree | 1e326f60da80f0c4ecd02c59fac49b2288d40d10 /var | |
parent | e2bec75057000887f5af7f66761527d86b7562f6 (diff) | |
download | spack-afbb4a5cbade91d0b80e39ecbd98051bb8fd7628.tar.gz spack-afbb4a5cbade91d0b80e39ecbd98051bb8fd7628.tar.bz2 spack-afbb4a5cbade91d0b80e39ecbd98051bb8fd7628.tar.xz spack-afbb4a5cbade91d0b80e39ecbd98051bb8fd7628.zip |
installation: skip repository metadata for externals (#16954)
When Spack installs a package, it stores repository package.py files
for it and all of its dependencies - any package with a Spack metadata
directory in its installation prefix.
It turns out this was too broad: this ends up including external
packages installed by Spack (e.g. installed by another Spack instance).
Currently Spack doesn't store the namespace properly for such packages,
so even though the package file could be fetched from the external,
Spack is unable to locate it.
This commit avoids the issue by skipping any attempt to locate and copy
from the package repository of externals, regardless of whether they
have a Spack repo directory.
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions