Hi All,
That's the idea.
An env.sh for each toolshed tool (or tool dependency). Everything is
generic and modular this way, while giving us better control over
versions, and control over compilation settings.
Here is something I've tried.
$INSTALL_DIR/bin
Hi Greg,
I am wondering the similar thing. If I understand Kevin's post correctly, I
think the question really is: if the automated tools build is
the requirement for creating the shed tool version specific env.sh
automatically during the shed tool installation.
Take BWA on the Tool Shed as an ex
Hi Kevin,
I'm not clear why you want to create a "dummy" env.sh file, so I may not be
able to answer your question. However, see the following tool shed wiki page
in case you want to create an env.sh file that is sourced when the tool(s)
included in the installed repository is executed in the
