Re: [galaxy-dev] Configurable toolshed package installation to support tool-dependency-resolver-plugins

2013-11-05 Thread Greg Von Kuster
I think that the best approach for this is an additional ToolDependency status as John proposed a while back as this approach allows for the flexibility needed to support just about anything users may want to do. I haven't had a chance to look at this yet, and I'm currently working on a couple

Re: [galaxy-dev] Configurable toolshed package installation to support tool-dependency-resolver-plugins

2013-11-04 Thread John Chilton
Simon, As you have probably noticed a new stable galaxy was released. It includes 95% of what we discussed including this implicit check to see if tool shed packages are enabled. Your help implementing, testing, and driving these changes was greatly appreciated! I couldn't however pull the

Re: [galaxy-dev] Configurable toolshed package installation to support tool-dependency-resolver-plugins

2013-10-14 Thread Guest, Simon
At Mon, 14 Oct 2013 20:22:06 -0500, John Chilton wrote: Simon, Very cool! I have two concerns. Rather than adding a new configuration option I think I would prefer to just check the configured dependency resolvers and then infer from them if the tool shed will be used. The configuration

[galaxy-dev] Configurable toolshed package installation to support tool-dependency-resolver-plugins

2013-10-10 Thread Guest, Simon
At Fri, 4 Oct 2013 23:12:01 -0500, John Chilton wrote: I understand the desire to not want to try to execute the tool shed actions if tool_shed_packages are not specified in the dependency resolvers list. I have created a Trello card for it (https://trello.com/c/CPeU3VlR). It sounds like the