With regard to Galaxy tools, a repository should only contain one
Hi all, I've just seen Greg's blog post, "The Galaxy Tool Shed: Best Practices for Populating a Repository" http://gregvonkuster.org/galaxy-tool-shed-best-practices-populating-reposito... One particular point that caught my attention (which I've used as the email title), which seems to signal a move away from "Tool Suites" as a single repository (although they can presumably be emulated by a dummy package defining dependencies on the child tools?). "With regard to Galaxy tools, a repository should only contain one." I look forward to future posts (or emails?) clarifying this... Regards, Peter
Hi Peter, On Feb 21, 2014, at 9:10 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi all,
I've just seen Greg's blog post, "The Galaxy Tool Shed: Best Practices for Populating a Repository"
http://gregvonkuster.org/galaxy-tool-shed-best-practices-populating-reposito...
One particular point that caught my attention (which I've used as the email title), which seems to signal a move away from "Tool Suites" as a single repository (although they can presumably be emulated by a dummy package defining dependencies on the child tools?).
"With regard to Galaxy tools, a repository should only contain one."
I look forward to future posts (or emails?) clarifying this…
Full clarification will be posted very soon….
Regards,
Peter ___________________________________________________________ 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: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
participants (2)
-
Greg Von Kuster
-
Peter Cock