Can someone remind me why we moved from the conda ...
# team-maintainers
j
Can someone remind me why we moved from the conda declaration in teh module to the separate environment.yml file? Was it something to do with seqera containers?
m
Nope
Personally I found this annoying when there's just the 1 tool
but when you have more than 5 tools, a yaml is much more easier to read than a 1 liner
j
I see, so it was to handle readability for multi tool environments?
Just that?
m
No idea
But for me that's an added bonus
j
Any one remember the history? 😅
m
Didn’t it have something to do with seqera containers? e.g, you can feed the yaml in
wave-cli
and get a container
j
I thought it was something like that, no?
m
ok, for me it was unrelated
It might have been that indeed
m
m
I thought @Edmund had something to do with it 😄
j
OK wave it is then
(and the bonus Maxime mentioned)
i
The PR is from 2023 and we still have to specify Docker and Singularity manually
r
I thought Edmund had something to do with it
always a safe bet
😆 3
😁 1
m
I do like the idea of moving container and conda declaration out of the modules
main.nf
though
m
"plans"
😁 1
i
Is there any module where this is already implemented? Certainly not the cited
fastqc
m
nope, not yet
p
I think it was so that we could use Renovate, to auto-bump the versions when new conda releases come out?
I don't think it has anything to do with Wave
image.png
🤣 5
Poor Wave wave containers 😰 😆
j
@Phil Ewels needs repost on #nf-core-memes
p
🫡