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
> make_install: just make; make install; allow providing make options
Is that not supposed to work with the 'setup_virtualenv'?
> 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
> -- 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:
> To search Galaxy mailing lists use the unified search at:
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:
To search Galaxy mailing lists use the unified search at: