Closed amizeranschi closed 5 years ago
Thanks for the question. You're right that tools from bcbiovm don't get linked into the main bin
directory, except for bcbio_vm.py itself. This is intentional, specifically to avoid overlinking files from the base bcbio installation where they overlap.
The calls to bcbio inject the right path in when running to avoid needing to symlink them:
and to keep it excluded. However, this is at the end of the path so if you have other tools installed that mask them it will use those first.
If it would be useful to symlink some high level tools, like Cromwell and cwltools, into the bin directory we could do.
Thank again for the discussion.
Thanks for the reply and the clarification. It might still be useful to symlink tools like cromwell, cwltool and toil (if it'll make it back into the bcbio tool-chain) inside the bcbio_nextgen/tools/bin
directory. This could help to prevent some situations such as the one mentioned here: https://github.com/bcbio/bcbio-nextgen/issues/2697#issuecomment-468956231.
Hi,
Not sure if this is intended, but I noticed that executables from some of the conda environments aren't getting symlinked into
bcbio_nextgen/tools/bin
. The ones from the bcbio-vm environment stood out to me, but others could be missing as well.In case it helps shed more light on this, below is a list of all the files that are in
bcbio_nextgen/tools/bin
: