Hi Wolfgang, You didn't include the name or a link to your Test Tool Shed packages. Are you talking about the suite_config.xml file? I'm not sure if Galaxy still uses that, no-one answered my earlier question: http://dev.list.galaxyproject.org/Role-of-suite-config-xml-in-current-Tool-S... https://lists.galaxyproject.org/pipermail/galaxy-dev/2014-October/020762.htm... e.g. https://github.com/peterjc/pico_galaxy/blob/master/tools/protein_analysis/su... https://github.com/peterjc/pico_galaxy/issues/5 Peter On Wed, Dec 10, 2014 at 10:18 AM, Wolfgang Maier <wolfgang.maier@biologie.uni-freiburg.de> wrote:
Dear all,
I'm currently testing a software package we developed for installation from the testtoolshed. Things seem to work fine mostly, but there is one thing I don't know how to solve (if it can be solved).
Our package consists of 14 individual tools, which I uploaded as 14 separate repositories together with a repository suite definition that's taking care of installing all tools.
Now, somewhat naively as it seems, I expected the order of repository declarations in the suite definition file to determine the order of the tools in the Galaxy Tools Bar, but, instead, they are added in seemingly random order.
So I'm looking for a way to predefine the final order of the tools so that it makes sense for a typical workflow. Any advice how to address this?
Thanks for your help, Wolfgang
___________________________________________________________ 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: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/