Project

General

Profile

Milestone #18410

Use successfully a non-trivial product relocated to a system where a dependency is a virtual package whose definition and/or location has changed.

Added by Christopher Green about 2 years ago. Updated over 1 year ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
12/07/2017
Due date:
12/07/2017
% Done:

0%

Estimated time:
Duration: 1

Description

Demonstrate successful use where the concrete product is, or is not, mentioned in packages.yaml.


Related issues

Precedes Spack Planning - Milestone #18411: Produce a Spack-based distribution of the canvas product stack art-precursor distribution on both toolchains and both platforms mentioned above.Accepted12/08/201712/08/2017

Follows Spack Planning - Milestone #18409: Use successfully a non-trivial product relocated to a system with a materially different pacakges.yaml.Accepted12/06/201712/06/2017

History

#1 Updated by Christopher Green about 2 years ago

  • Precedes Milestone #18411: Produce a Spack-based distribution of the canvas product stack art-precursor distribution on both toolchains and both platforms mentioned above. added

#2 Updated by Christopher Green about 2 years ago

  • Related to Milestone #18409: Use successfully a non-trivial product relocated to a system with a materially different pacakges.yaml. added

#3 Updated by Christopher Green about 2 years ago

  • Related to deleted (Milestone #18409: Use successfully a non-trivial product relocated to a system with a materially different pacakges.yaml.)

#4 Updated by Christopher Green about 2 years ago

  • Follows Milestone #18409: Use successfully a non-trivial product relocated to a system with a materially different pacakges.yaml. added

#5 Updated by Christopher Green almost 2 years ago

Risk items:

  • It may not be possible to handle this case.
  • Relocation in the context of any virtual package dependencies may not be possible generally.
  • It is also uncertain in the wider sense how one would handle systems where different variants of a system depend on different concrete providers of a virtual package.

#6 Updated by Christopher Green over 1 year ago

  • Status changed from New to Accepted


Also available in: Atom PDF