Designing and maintaining an up-to-date set of packages.yaml for some target machines
While we are accessing to common machines (plafrim, occigen, curie) or systems (Debian), we indivually set up our compilers.yaml and packages.yaml files.
We maintain these configuration files for a well defined (and documented) set of machines
- To be discussed
** Separate git repository? We might want to have a separate git repository for that since:
- a user may want to use a given release or git version of solverstack;
- but get access to the most up-to-date compilers.yaml and packages.yaml files as machine set ups are continuously evolving (system updates, ...).
** Which machines?
- basic linux system (Debian-based?, with Cuda and Intel MKL?)