On Thu, Jul 31, 2014 at 12:29 PM, Peter Cock p.j.a.c...@googlemail.com wrote:
On Thu, Jul 31, 2014 at 5:21 PM, bjoern.gruen...@googlemail.com
bjoern.gruen...@gmail.com wrote:
Hi Peter,
2014-07-31 10:57 GMT+02:00 Peter Cock p.j.a.c...@googlemail.com:
Hi Dave,
You are right that on closer
Hi Dave,
You are right that on closer inspection I've mixed tool_dependencies.xml
and repository_dependencies.xml *again*. Evidentially my mental model
does not match Greg's here:
(*) I need to define a tool installation recipe for something not in the
Tool Shed -- write an install script called
Hi Peter,
2014-07-31 10:57 GMT+02:00 Peter Cock p.j.a.c...@googlemail.com:
Hi Dave,
You are right that on closer inspection I've mixed tool_dependencies.xml
and repository_dependencies.xml *again*. Evidentially my mental model
does not match Greg's here:
(*) I need to define a tool
On Thu, Jul 31, 2014 at 5:21 PM, bjoern.gruen...@googlemail.com
bjoern.gruen...@gmail.com wrote:
Hi Peter,
2014-07-31 10:57 GMT+02:00 Peter Cock p.j.a.c...@googlemail.com:
Hi Dave,
You are right that on closer inspection I've mixed tool_dependencies.xml
and repository_dependencies.xml
Hi all,
I'm not sure when this started (having hardly looked at my Tool Shed
test results since GCC2014), but I think this is a fairly recent problem
with my BLAST RBH tests failing (which has held me back from posting
this to the main Tool Shed).
This could be some silly mistake in my tar-ball,
Peter,
I believe part of the problem is that the install and test framework is unable
to resolve the dependency on blast+ 2.2.29 because it is defined as a
repository dependency, not a tool dependency. I would recommend replacing the
repository dependency in the blast_rbh repository with a
