I've got several custom tools that are going to be published on the toolshed but are not currently. Right now they hard-code the paths to the tool dependencies, but I was wondering if there's a way to handle their dependencies with a tool_dependencies.xml like toolshed tools have? A colleague told me that tool dependencies can't be handled for tools that didn't come from a tool shed, but I wanted to double-check this.
Heads up! This is a static archive of our support site. Please go to help.galaxyproject.org if you want to reach the Galaxy community. If you want to search this archive visit the Galaxy Hub search
Question: Can Dependencies Be Handled in Custom Tools?
0
mccoykg • 80 wrote:
ADD COMMENT
• link
•
modified 3.0 years ago
by
Jennifer Hillman Jackson ♦ 25k
•
written
3.0 years ago by
mccoykg • 80
0
Jennifer Hillman Jackson ♦ 25k wrote:
Hello,
Any tool can have an associated tool_dependencies.xml file. This would be needed anyway before loading your new tools into the Tool Shed. (Not strictly required, but it is a better model to follow).
However, if the goal is to allow others to install the tool outside of a tool shed with managed dependencies, using the same mechanisms specific to those installed from a tool shed, then your colleague is correct.
https://wiki.galaxyproject.org/ToolShed
Thanks, Jen, Galaxy team
Thanks! So what would be the correct mechanism for managing dependencies for tools outside of a toolshed / in the "tools" folder of an instance?
Please log in to add an answer.
Use of this site constitutes acceptance of our User
Agreement
and Privacy
Policy.
Powered by Biostar
version 16.09
Traffic: 166 users visited in the last hour