Re: [Bioc-devel] Why can't NAMESPACE be a strict subset of DESCRIPTION Imports?

2016-10-05 Thread Martin Morgan
On 10/04/2016 05:09 PM, Martin Morgan wrote: On 10/04/2016 05:07 PM, McDavid, Andrew wrote: BiocCheck throws a warning when a package is listed as Imports: in DESCRIPTION but not used in the NAMESPACE. This may happen when a developer uses the fully qualified names of objects within a package.

Re: [Bioc-devel] Why can't NAMESPACE be a strict subset of DESCRIPTION Imports?

2016-10-04 Thread Dan Tenenbaum
- Original Message - > From: "Martin Morgan" <martin.mor...@roswellpark.org> > To: "McDavid, Andrew" <andrew_mcda...@urmc.rochester.edu>, "bioc-devel" > <bioc-devel@r-project.org> > Sent: Tuesday, October 4, 2016 2:09:27 PM

Re: [Bioc-devel] Why can't NAMESPACE be a strict subset of DESCRIPTION Imports?

2016-10-04 Thread Martin Morgan
On 10/04/2016 05:07 PM, McDavid, Andrew wrote: BiocCheck throws a warning when a package is listed as Imports: in DESCRIPTION but not used in the NAMESPACE. This may happen when a developer uses the fully qualified names of objects within a package. I am unclear as to the rationale for this

[Bioc-devel] Why can't NAMESPACE be a strict subset of DESCRIPTION Imports?

2016-10-04 Thread McDavid, Andrew
BiocCheck throws a warning when a package is listed as Imports: in DESCRIPTION but not used in the NAMESPACE. This may happen when a developer uses the fully qualified names of objects within a package. I am unclear as to the rationale for this warning. Per Hadley: It's common for packages