What's the latest on pinning conda channel version...
# modules
p
What's the latest on pinning conda channel versions? I've been removing some but I just realised that the docs say that we should use them: https://nf-co.re/docs/guidelines/components/modules#use-of-conda-directive Is there any benefit when the
environment.yml
file has the conda channels already?
j
Yes, because you can't always know the exact priority path
s
I've been requiring the channel to be specified.
👍 1
p
This is in case the package ends up in both bioconda and conda-forge?
this 1
s
I guess so. I have a feeling there might have been one instance of that
image.png
(although they say they are the same version) This one is more different:
p
Yeah it's happened a few times
Question is whether always pinning all packages to a channel does any harm, I guess not 🤔
e
Just obscures instances where it's actually necessary to specify the channel like argparse
p
or on the other hand, protects you against those cases (like in Angel's arm64 talk example earlier with
fq
)
👍 2
👍🏻 1