Moving the Galaxy tools into the Tool Shed or the IUC account

[bgruening]

Hi John,

it would be nice if we could move your tools to the Galaxy Tool Shed so that others can easily install your awesome wrappers! If you want to share the burden, please feel free to join larger communities like:

• https://github.com/galaxyproject/tools-iuc
• https://github.com/bgruening/galaxytools

We have some CI-testing and review process established and try to maintain these wrappers long-term.

Thanks, Bjoern

[jmeppley]

Thanks Bjoern! I would love to move them into the tool shed. I have them installed in a private toolshed, but I didn't want to release to the public until I work out how to get all the necessary packages bundled or configured as dependencies. It's a long list.

I'm also not sure of the best way to handle the big public databases. Many tools depend on some of the big public DBs (RefSeq, Silva, etc). These have to be installed locally for most of the tools to be useful. Currently it has to be done manually (with the provided Makefile). This could be run as part of the toolshed install process, I guess, but the makefile is so prone to failure and it's hard to get useful feedback to the user in the toolshed install process, that I'm sure lots of people will end up with a broken installation and no idea why. Another way to go would be to set up a galaxy workflow to create the databases, but that would require new tools for the database build and that the user import the database into her/his history every time.