What EasyBuild Is Doing¶
A recipe. A stack. A test.
EasyBuild’s documentation is good at what to type. This book is the file, the tree, and the run.
A journey is a how-to path over pages that already exist.
First recipe — read a file, then the four mechanisms
A build failed — the log, then the usual causes
Port a package — conda-forge or Spack in, an easyconfig out
Write a test — four kinds, then a ReFrame class
The same pages, grouped by kind of reading: the recipe, the stack, the test. The path, the papers, and how the samples run are at the back.