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 Galaxy instance in case 
this is what you're looking for.

http://wiki.galaxyproject.org/ToolShedToolFeatures#Finding_dependencies_included_in_an_installed_repository_at_tool_execution_time

Greg Von Kuster


On Nov 12, 2012, at 1:51 AM, Kevin Y wrote:

> Hi dev list,
> 
> What is the simplest xml I can put into a tool_dependencies.xml
> for it to create a dummy env.sh in tool-dependency/tool/version/
> ..../awef234243/env.sh
> 
> And will this be sourced each time. Or does the dependency need to be
> some sort of "successfully install" status for it to be sourced?
> 
> Ideally I would be elegant if there is a way to create this env.sh
> easily as it's the best way for a galaxy admin to manage the different
> versions of dependencies.
> 
> Thanks,
> Kevin.
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> 
>  http://lists.bx.psu.edu/


___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

  http://lists.bx.psu.edu/

Reply via email to