Hi Peter, On Aug 7, 2013, at 10:26 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hi Greg et al,
For the NCBI BLAST+ wrappers, Nicola has suggested we split out the binaries themselves into a separate Tool Shed package, e.g. package_blast_plus_2_2_26 and similar for the later releases.
https://github.com/peterjc/galaxy_blast/issues/7
I think this is a good idea.
I agree.
I'd like to check if there are any complications foreseeable from the fact that the NCBI BLAST+ wrappers were migrated out of the Galaxy core and therefore have migration scripts we need to consider.
I don't think this change will affect the Galaxy tool migration process for the ncbi_blast_plus repository since the migration script defines revision d375502056f1 of the repository. SInce that is an installable revision, the migration process will install that revision only, and additional revisions of the repository requires separate installation.
Potentially this could be held under the shared IUC account as planned for other commonly used packages? Or would the migration issues require it to also live under devteam?
I think using hte iuc account would be best - again, this should have no effect on the migration process.
Also, we may wish to add a dependency on BOOST, e.g. http://testtoolshed.g2.bx.psu.edu/view/iuc/package_boost_1_53 once this is on the main Tool Shed.
Sounds great!
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/