On Sat, Nov 1, 2014 at 2:30 AM, Ross ross.lazarus@gmail.com wrote:
Hi, Bruno. As Björn points out, cross-toolshed dependencies aren't currently supported but exporting (eg) package_r_3_1_1 as a capsule (make sure to include ALL dependencies) from one toolshed and importing that capsule into your own local toolshed brings all the sub-dependent packages so they exist locally. One trick: if the toolshed URL is NOT specified in a package reference in tool_dependencies.xml, the local toolshed will be sourced as the default. Not sure if this makes much sense, but it works for me developing on my laptop's toolshed with lots of packages that came through capsules from the main and other tool sheds.
Yes, I make heavy use of the default tool-shed attribute so that I can upload the same XML file to either the Test Tool Shed or the main Tool Shed. The only catch is making sure all the dependencies are in both.
Peter