Matthieu Muffato

> I think this also indicates support only for cross-organisational modules and not cross-organisational subworkflows? Currently, yes > I'm very wary of increasing the idiosyncrasies in the code and I...

I've given you, @mirpedrol , write access to repo. I'd prefer we continue the review here rather than #3456 so that all the review history is in one place

@awgymer What CI testing is missing ? This includes does include tests for the new cross-repo functionality. That's in fact how it was developed: @jvfe first wrote (failing) test cases...

Ah right. Well, it sounds like it is a good idea for another internship/mentorship ;) a `nf-core` command to install missing cross-org modules so that tests can then run.

It's there already: https://github.com/nf-core/tools/pull/3083/files#diff-60cea8a0cf3a284ef26219e6dc9b9b2b55ebb25214cb520b0ae38ef6179436d7R87 It uses modules/subworkflows across nf-core/modules and https://github.com/nf-core-test/modules

Thank you everyone ! 

Hi @vsoch . The use case is still the same as in https://github.com/singularityhub/singularity-hpc/issues/501#issuecomment-1065818554 . Following up on > I figured most folks would install the latest and call it a...

Is this the interface you're proposing ? ``` shpc install software[:version] # Install the software, either the latest version or the one specified shpc install software --upgrade [--dry-run] # if...

`shpc install software` 1) doesn't uninstall older versions, 2) doesn't replicate the views of previously installed versions

The analogy is homebrew, which offers: ``` brew list [FORMULA|CASK...] brew install FORMULA|CASK... brew reinstall FORMULA|CASK... brew uninstall FORMULA|CASK... brew update brew upgrade [FORMULA|CASK...] ``` `shpc` already has `list [software]`,...