Hi James, thanks for your thoughts on abstraction of common tasks. For most of these things we have now patches in bitbucket.
Similar recipes could be:
autoconf: default to configure; make; make install, allow providing configuration options
https://bitbucket.org/galaxy/galaxy-central/pull-request/218/implementation-...
make_install: just make; make install; allow providing make options
https://bitbucket.org/galaxy/galaxy-central/pull-request/217/implementation-...
python_virtualenv
Is that not supposed to work with the 'setup_virtualenv'?
ruby_rbenv
From John: https://bitbucket.org/galaxy/galaxy-central/pull-request/207/john-chiltons-a...
r_package
https://bitbucket.org/galaxy/galaxy-central/pull-request/219/implementation-... Cheers, Bjoern
...
Basically, most of the times the steps to install a particular package are boilerplate, this would remove a ton of duplication in the recipe files. Also, a likely less popular proposal would be to go one step further, tool_dependencies.yaml:
recipe: python_package_setuptools name: requests version: 1.2.3 url: http://pypi.python.org/packages/source/r/requests/requests-${version}.tar.gz
-- jt ___________________________________________________________ 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/