Re: [Bioc-devel] modify _R_CHECK_FORCE_SUGGESTS_ ?

On Fri, May 18, 2018 at 2:26 PM, Martin Morgan wrote: > You can create a plain text file in the root directory of your package > .BBSoptions with the line > > UnsupportedPlatform: win > > Your package will not be available on Windows, losing about 1/2 your >

Re: [Bioc-devel] modify _R_CHECK_FORCE_SUGGESTS_ ?

You can create a plain text file in the root directory of your package .BBSoptions with the line UnsupportedPlatform: win Your package will not be available on Windows, losing about 1/2 your potential audience. A better strategy is to figure out why you are Suggests:'ing Rsubread, and find

Re: [Bioc-devel] modify _R_CHECK_FORCE_SUGGESTS_ ?

I guess I was unclear. what I was asking is if it is, e.g., *required* for your vignette, e.g. to create a data structure that is then used by your functions. That is a pretty standard use of Suggests, though obviously not the only one. My point was really that the package only being suggests is

Re: [Bioc-devel] modify _R_CHECK_FORCE_SUGGESTS_ ?

Only if Rsubread is used unconditionally. On Fri, May 18, 2018 at 2:00 PM, Gabe Becker wrote: > Vivek, > > Why (ie in what sense) is the package suggested? Is it used in your tests, > examples, or vignette? > > If so, those would also fail during R CMD check if the package

Re: [Bioc-devel] modify _R_CHECK_FORCE_SUGGESTS_ ?

Vivek, Why (ie in what sense) is the package suggested? Is it used in your tests, examples, or vignette? If so, those would also fail during R CMD check if the package is not available even if that environment variable is were false, wouldn't they? ~G On Fri, May 18, 2018 at 1:55 PM, Bhardwaj,

[Bioc-devel] modify _R_CHECK_FORCE_SUGGESTS_ ?

Hi All My package is in review and the build is failing since a suggested package (Rsubread) is not available on windows. Is there a way for me to instruct the build machine on bioc to use: _R_CHECK_FORCE_SUGGESTS_ = FALSE ?? Best, Vivek Vivek Bhardwaj PhD Candidate |

Re: [Bioc-devel] typo on website 'install' page

Thank you. This is corrected and should be reflected shortly. Lori Shepherd Bioconductor Core Team Roswell Park Cancer Institute Department of Biostatistics & Bioinformatics Elm & Carlton Streets Buffalo, New York 14263 From: Bioc-devel

Re: [Bioc-devel] BiocInstaller: next generation

On 05/18/2018 03:28 AM, Neumann, Steffen wrote: Hi, On Wed, 2018-05-09 at 18:11 -0400, Martin Morgan wrote: ... - version() version of Bioconductor in use - valid() are all Bioconductor packages from the same Bioconductor version? I'd like to challenge the concept of the release and

[Bioc-devel] typo on website 'install' page

On the Install page, https://www.bioconductor.org/install/, I just noticed that in the box on the right hand side, the "Worflow packages" link is misspelled (missing 'k'). --t [[alternative HTML version deleted]] ___ Bioc-devel@r-project.org

Re: [Bioc-devel] BiocInstaller: next generation

On Fri, May 18, 2018 at 3:28 AM, Neumann, Steffen wrote: > Hi, > > On Wed, 2018-05-09 at 18:11 -0400, Martin Morgan wrote: > > > > ... > >- version() version of Bioconductor in use > >- valid() are all Bioconductor packages from the same > > Bioconductor > >

[Bioc-devel] Build error in tokay2: cannot reserve space for vector

Dear Bioconductor team,  I'm the maintainer of the FELLA package.  Lately the check in tokay2 has failed, see http://bioconductor.org/checkResults/release/bioc-LATEST/FELLA/tokay2-checksrc.html Specifically: Message: At vector.pmt:442 : cannot reserve space for vector, Out of memory Class:

Re: [Bioc-devel] BiocInstaller: next generation

Hi, On Wed, 2018-05-09 at 18:11 -0400, Martin Morgan wrote: > > ... >- version() version of Bioconductor in use >- valid() are all Bioconductor packages from the same > Bioconductor > version? I'd like to challenge the concept of the release and the pretty strong term valid(). I think