Good day,
R's checking may encourage a dependency on R to be placed in the DESCRIPTION
file, based on examining the data files distributed with the package. For
ClassifyR, I get a warning if the dependency is absent.
* checking data for ASCII and uncompressed saves ... WARNING
Warning:
rts/Suggests/Enhances:” fields: --> Depends
From: Bioc-devel on behalf of Martin Morgan
Sent: Monday, January 14, 2019 6:52 PM
To: Lulu Chen; bioc-devel@r-project.org
Subject: Re: [Bioc-devel] support the stable version of R
Remember that Bioconductor pac
Probably my rant yesterday was a bit confused.
BiocCheck tries to encourage better practice. If you've chosen to specify
version (maybe there are reasons for this, e.g., because in the past you have
distributed your package through non-Bioconductor channels), then specify it
correctly.
On the
Martin,
> Having said that, I'll note that specifying R as a dependency, and a
version of R as a criterion for your package, is really a mis-nomer for a
Bioconductor package -- of course it uses R, and the version of R in use
determines the Bioconductor version(s) that can be used! So a rational
Maybe a little more helpfully, I think you should create a branch for 'before'
Bioconductor, where you can specify R version dependency as you see fit.
Indeed, at each release the version of your package at git.bioconductor.org
will have a branch created for that release, e.g., the RELEASE_3_8
Remember that Bioconductor packages are tested nightly on our build system, and
this nightly testing is an important component of offering your users a stable
environment, not just for your package but the other packages they use.
Recreating this standard environment is facilitated by the
Dear all,
When submitting package to bioconductor, it is required to change R version
in "Depends" to be >= the develop version (3.6) . As my package is also
available in GitHub, someone asks if it be possible to make it available
with the stable version of R (R3.5). In fact, my package can work
