[Bioc-devel] request for more notices about build issues

Sean Davis seandavi at gmail.com
Wed Apr 8 20:33:35 CEST 2015

Is this a use case for a "graphical" build report that displays the build
status on a graph/DAG?


pkgDepTools, combined with a computable build report (a downloadable
version of the current build report), might allow a graphical (in both node
and edge as well as visual) build report.  I could envision a color scheme
applied to a figure like the last figure in the PDF above.  A little
functionality could be built to find the "root" of a build problem for any
specific package (to the extent that pkgDepTools can capture the

This is not a well-thought-out answer, so take it with a grain of salt.


On Wed, Apr 8, 2015 at 2:03 PM, Michael Love <michaelisaiahlove at gmail.com>

> dear core Bioc-ers,
> It would be nice to have more devel mailing list notices about large
> scale build issues, just to keep developers in the loop. (e.g. I often
> get a number of emails when GenomicRanges is down, asking why I'm
> breaking someone's downstream package).
> Or if you don't want to "push" these out to the list, to have a URL
> where core team could post information about what's going on in devel
> and rough timelines about upcoming changes. Then developers can "pull"
> this information when they need to.
> thanks for all your work! There are lots of exciting things in the
> next release, and I know that's it's a lot of work to get to the
> finish.
> best,
> Mike
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel

	[[alternative HTML version deleted]]

More information about the Bioc-devel mailing list