Matthieu Muffato

Moving this from "Triage" to "Todo" as recent experience with hard-to-run Buscos confirms we want to be able to take a pre-existing Busco result as output.

The code is there, but I still need to add unit-tests and documentation

Hi @ewels . Unfortunately there's too much work left to do on this PR. I can't see myself getting to the bottom of it any time soon.

I propose to modify `nf_core/download.py` to: 1. First check `$NXF_SINGULARITY_LIBRARYDIR` and use it, while explicitly forbidding `--container-cache-utilisation amend`. No automatic creation of `$NXF_SINGULARITY_LIBRARYDIR` would be considered. 2. Otherwise use `$NXF_SINGULARITY_CACHEDIR`...

`NXF_SINGULARITY_LIBRARYDIR` is the read-only version of `NXF_SINGULARITY_CACHEDIR`. Nothing needs to change in the way modules, Singularity URLs, etc, are written. Internally, files can be copied from the library the same...

I think `pipe` should be a property of each input/output channel. For instance, for an aligner it's likely that its input reference genome would _not_ be `pipe`-able (because random seeks...

> Nextflow 22.04 brings with it Did you mean 24.04 ?

Thank you all ! 

My concern is that several of the changes require Nextflow 24.04. It means that from this point forward, nf-core will only support Nextflow 24.04+. Is there an analysis of 24.04...

Oh yes @ewels , I don't deny the advantages of moving over. There will be a lot of benefits for people to move. Hopefully we can get away with it...