Hi Peter,
This feature has been on my list for some time. There was discussion about this at the Galaxy Community Conference in July, and the priority for providing this was raised at that time. However, my next chunk of work will be in the area of enhancing the Galaxy framework to better handle locating certain tool-related items at tool execution time (e.g., Java jar files and other files on which tools depend). When this is finished, the next major chunk of work on my list is this feature you're requesting below.
I'm hopeful that I can get started on this within the next couple of weeks. I have the implementation worked out in my head, and I don't think it will take too long to finish once I can get started. I'll keep you and the community informed as progress is made.
Greg Von Kuster
On Aug 23, 2012, at 9:12 AM, Peter Cock wrote:
Dear all,
Is there any way for a Tool Shed bundle (or individual tool) to declare a dependency on another Tool Shed bundle (and ideally a minimum version) which provides a datatype?
For example, the 'emboss_5' suite depends on the 'emboss_datatypes' entry. Likewise the ncbi_blast_plus suite depends on 'blast_datatypes' to define the 'blastxml' format (and soon nucleotide and protein BLAST databases).
As a specific case, I'd like to update my 'blast2go' wrapper to say it now also depends on blast_datatypes because it uses the 'blastxml' format.
Similarly some of my sequence filtering/selection tools could be expanded to handle other formats like 'genbank', which is defined in the 'emboss_datatypes' repository.
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: