[Bioc-devel] Announcing newtest coverage shields

2015-06-24 Thread Dan Tenenbaum
Hello Bioconductors, We're pleased to announce a new shield to join the ones we rolled out in May. The new shield measures test coverage of a package, as determined by Jim Hester's covr package. Coverage is a measure of the degree to which package code is tested by your unit tests

Re: [Bioc-devel] Announcing newtest coverage shields

2015-06-24 Thread Henrik Bengtsson
On Wed, Jun 24, 2015 at 5:42 PM, Dan Tenenbaum dtene...@fredhutch.org wrote: Hello Bioconductors, We're pleased to announce a new shield to join the ones we rolled out in May. The new shield measures test coverage of a package, as determined by Jim Hester's covr package. Coverage is a

Re: [Bioc-devel] best practice: dependencies of dependencies / no visible global function definition

2015-06-24 Thread Martin Morgan
On 06/24/2015 10:42 AM, Michael Lawrence wrote: In order for R to find those symbols reliably, you need to import those functions into your NAMESPACE, and therefore you should ensure yes that the Biobase package is listed on the Depends line of your DESCRIPTION. Your package directly depends

[Bioc-devel] best practice: dependencies of dependencies / no visible global function definition

2015-06-24 Thread Ludwig Geistlinger
I'm surely not the first asking this question. But as I did not find a clear answer to that (e.g. in the 'Writing R extensions' manual or in the diverse posts on this), I risk asking it again. As an example: I'm dealing a lot with ExpressionSets (from Biobase) and GeneSet[Collection]s (from

Re: [Bioc-devel] best practice: dependencies of dependencies / no visible global function definition

2015-06-24 Thread Michael Lawrence
In order for R to find those symbols reliably, you need to import those functions into your NAMESPACE, and therefore you should ensure that the Biobase package is listed on the Depends line of your DESCRIPTION. Your package directly depends on Biobase, so there's no redundancy by having it listed