https://nf-co.re logo
Join Slack
Powered by
Thoughts <!here>?
# team-maintainers
j
Thoughts <!here>?
e
Just update imo...any users of old BIGSLICE will just not receive the updates, until they manually update to BIGSLICE_BIGSLICE, correct? Nothing really breaks
j
Correct
B ut they may get errors of 'module not found' or something
when running 
nf-core modules update
I don't know how extensive the errors will be... any idea @mashehu?
m
Iā€™d say go for it šŸ¤·šŸ» a quick google search should fix any downstream issues
šŸ‘ 3
šŸ‘šŸ» 1
p
Go for it šŸ‘šŸ»
j
OKY DOKY
p
Small maybe pain now to avoid big certain pain later
100 rainbow 2
j
Thank you, I blame you all if someone complains at me šŸ˜‰
p
That's what I'm here for!
šŸŽÆ
shared a GIF
šŸ˜† 1
j
I was aiming it at @Evangelos Karatzas but you'll do as a backup
šŸ›”ļø 1
ā¤ļø 1
šŸ˜… 1
m
feel free to pass the blame, also used to it šŸ¤·šŸ»
j
Maybe we should add something to the tooling 
you asked for bigslice, did you mean bigslice/bigslice?
šŸ‘ 1
100 rainbow 1
šŸ‘šŸ» 1
s
Yeah, that'd be really helpful if the tooling did a search after it didn't find a module
m
i think I have an idea how to do this. but first want to finish the container conversion commands
ā­ 2
n
We've done it before with a massively used module (VEP) and it caused no issues so it will definitely be fine for this one šŸ™‚
šŸ‘ 2
2 Views
Open in Slack
PreviousNext
Powered by