Matthieu Muffato

Hi @vsoch . I found that `shpc view install $view $module` too does a core installation transparently, and it is a design choice: https://github.com/singularityhub/singularity-hpc/blob/main/shpc/client/view.py#L167-L168 which gives 3 ways of installing...

Still some work to do (and I need to fix the tests !) but `shpc reinstall` works. Could I get a review on it, @vsoch ? There's also one difficulty...

I was not aware of this CernVM-FS for biocontainers. That's really cool ! I really like the principle of this idea, especially as the containers my team manages largely overlap...

The discussion was going towards: "the containers are there, great, let's just use `shpc add` to use them, but you'll have to fill in the aliases in container.yaml" I think...

Let's say I've got this CernVM-FS on my cluster, and I want to install software from the official shpc registry, e.g. [samtools:1.15--h3843a85_0](https://github.com/singularityhub/shpc-registry/blob/main/quay.io/biocontainers/samtools/container.yaml#L13). samtools is already there on the filesystem, at...

Overlap between the containers used in the shpc registry and this cvmfs server ? I think they have all of conda-forge and bioconda channels

(no rush on my side. maybe wait for @audreystott to comment ? I may be pushing you in a different direction from what she'd like)

They're both used: - Module in uninstall functions and as a base class - RegistryModule in install functions RegistryModule expands Module by getting its configuration from the Registry / container.yaml

There is already the concept of a registry entry in [ContainerConfig](https://github.com/singularityhub/singularity-hpc/blob/main/shpc/main/container/config.py#L71-L80) although the `entry` variable is meant to be a `Result`, see [here](https://github.com/singularityhub/singularity-hpc/blob/main/shpc/main/modules/base.py#L206-L208) and [there](https://github.com/singularityhub/singularity-hpc/blob/main/shpc/main/client.py#L103-L106), and is also called "entry"...

> What is the reason we cannot maintain one Module object, which can either be in the process of creation (RegistryModule) or assume already created (Module?) Something quite silly. All...