On Wed, 20 Apr 2016, Andreas Tille wrote: > Hi Afif,
> On Tue, Apr 19, 2016 at 10:12:40PM -0700, Afif Elghraoui wrote: > > > and the reason is given in the description of the task: > > > Note that there is no according metapackage created since the packages > > > might be to different to make sense to install all on one machine. > > > I think this reason has a point - so we come back to the discussion how > > > to get a sensible dependency between cwltool and our tasks ... > > With the current setup, it seems like the answer should be to create > > another metapackage for workflow management systems. Of the entries > > currently in science-tools, at least pegasus-wms, snakemake, and cwltool > > could go directly in there. Then both our tasks and science-tools can > > refer to this new metapackage. > I like this idea. Feel free to do exactly this. :-) FWIW +1 on that additional candidates for inclusion if it would be a generic umbrella for all workflow management systems: python-nipype coop-computing-tools -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
