Message-ID: <1940199654.3343329.1412019122985.JavaMail.root@fhcrc.org>
Date: 2014-09-29T19:32:02Z
From: Dan Tenenbaum
Subject: [Bioc-devel] Workflows
In-Reply-To: <4332_1412018755_5429B243_4332_4764_1_6BB17839-2E2E-4019-95CC-D5CBFA6F3828@embl.de>
----- Original Message -----
> From: "Wolfgang Huber" <whuber at embl.de>
> To: bioc-devel at r-project.org
> Sent: Monday, September 29, 2014 12:24:54 PM
> Subject: [Bioc-devel] Workflows
>
>
> Sorry if I have overlooked something? referring to
> http://www.bioconductor.org/developers/how-to/workflows Is there a
> standardized way to manage
> - dependencies
> - versions
>
> In principle, these could be automagically computed (?), but would
> still have to be exposed to workflow users using an afaIcs not yet
> existing mechanism (?)
The builder simply notes any package that you invoke with library() or require() and then it creates a package and makes sure these packages are all added as dependencies in the DESCRIPTION file.
Dan
>
> Wolfgang
>
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>