Hello Fabien, I don't understand the issue - can you provide a sample tool config that includes these hard-coded paths? This initially sounds like an issue with the tool configs, not the tool shed, but I may see the problem with your clarification. Thanks, Greg Von Kuster On Jul 3, 2012, at 9:58 AM, Fabien Mareuil wrote:

Hi,

I have read the exchange betwen you and Florent Angly about "Problem with new tool shed" and I have a problem with Nebula Tools: http://nebula.curie.fr/. At the Pasteur Institute, we have 4 galaxy instances and I would like to use a local tool shed instance for Nebula installation. However, the nebula has tools with hard-coded path tool but I don't want hard-coded this so do you have a solution to add a thing like this ${tool.install_dir} in the xml?

Thank you for your answer. Best Regards,

Fabien Mareuil

___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:

http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists, please use the interface at:

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