Project

General

Profile

Milestone #18399

Build a small set of products, move and then build a new product against them.

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

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

0%

Estimated time:
40.00 h
Duration: 1

Description

Build a small set of products, move them using the buildcache facility and then attempt to build a new product with the relocated products as dependencies. Demonstrate this on Linux and on MacOS.

Related issues

Related to Spack Planning - Milestone #18406: Configure the current environment to be able to use a product.Accepted11/30/201711/30/2017

Precedes 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

  • Subject changed from Demonstrate the ability to build a small set of products, moveand then build a new product against them. to Build a small set of products, move and then build a new product against them.

#2 Updated by Christopher Green about 2 years ago

  • Description updated (diff)

#3 Updated by Christopher Green about 2 years ago

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

#4 Updated by Christopher Green about 2 years ago

  • Follows Milestone #18408: Set up multiple products for use by referring directly only to an umbrella product. added

#5 Updated by Christopher Green about 2 years ago

  • Related to Milestone #18406: Configure the current environment to be able to use a product. added

#6 Updated by Christopher Green about 2 years ago

  • Follows deleted (Milestone #18408: Set up multiple products for use by referring directly only to an umbrella product.)

#7 Updated by Christopher Green about 2 years ago

  • Estimated time set to 40.00 h

Risk items:

  • Possibility of unforeseen issues when trying to build against a relocated product.
  • Relocating the compiler is tricky and requires special setup once the compiler has been relocated (Patrick has details).
  • Products will have to be chosen carefully to demonstrate all aspects of desired behavior.
  • This milestone does not address the situation of materially different packages.yaml files on compile vs install platform.

#8 Updated by Christopher Green over 1 year ago

  • Status changed from New to Accepted

Also available in: Atom PDF