Aaron, Repository suite definitions are designed to only allow the latest revision to be installable. My recommendation in this case would be to define two separate suites tagged in some descriptive way, so the individual use cases would have their appropriate suites. - Dave Bouvier http://galaxyproject.org http://usegalaxy.org On 10/29/2015 02:23 PM, Aaron Petkau wrote:
Hello,
I'm running into some issues with maintaining multiple installable revisions for a repository suite and I'm not sure if there's something I've missed.
I have a local toolshed where I'm maintaining my tools, and I have a repository suite definition, defining a number of dependencies. So, I have:
suite_X (mercurial revision 0): Dependency A Dependency B
I updated "suite_X" and changed the dependencies:
suite_X (mercurial revision 1): Dependency A Dependency B Dependency C
I would like to have both mercurial revision 0 and 1 installable in Galaxy, but only revision 1 (the latest) is showing up as installable. I found documentation at https://wiki.galaxyproject.org/RepositoryRevisions but this seems to only cover a repository containing a single tool, not a suite of tools.
Is there something I'm doing wrong or some setting I have to change here? My toolshed is running with Galaxy tag "v15.07".
Thanks,
Aaron
___________________________________________________________ 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/