& Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
From: Bioc-devel on behalf of Alexey
Sergushichev
Sent: Tuesday, February 20, 2018 4:26:35 AM
To: Vincent Carey
Cc: bioc-devel@r-project.org
Subject: Re: [Bioc-devel] R version check in BiocChech
&
> It _is_ the developer's choice. But a developer of packages for the
Bioconductor
> project commits to using R-devel during certain pre-release phases,
depending
> on proximity in time to a point release of R. (See
http://bioconductor.org/developers/how-to/useDevel/)
> for full details.) BiocCh
On Mon, Feb 19, 2018 at 11:27 AM, Alexey Sergushichev
wrote:
> Kevin,
>
> > It does not request users to make R-devel a _requirement_ of their
> package.
>
> Sadly it does for new packages. New packages submitted to Bioconductor 3.7
> are _required_ to have R >= 3.5 dependency, otherwist BiocChec
> > Personally, I haven't found it to be particularly difficult to update R,
> > or to run R-devel in parallel with R 3.4, even without root privileges.
>
> I find it much harder for a normal user to install R-devel (and update
> it properly, because it's a development version) and running
> '
Kevin,
> It does not request users to make R-devel a _requirement_ of their
package.
Sadly it does for new packages. New packages submitted to Bioconductor 3.7
are _required_ to have R >= 3.5 dependency, otherwist BiocCheck will result
in a warning (
https://github.com/Bioconductor/BiocCheck/blob
I'll just throw in my two cents here.
I think many people underappreciate the benefits of moving to the latest
version of R. If you inspect the R-devel NEWS file, there's a couple of
nice fixes/features that a developer might want to take advantage of:
- sum() doesn't give NAs upon integer over
Hi Alexey,
I do agree with you that there is no harm in testing against other version
of R. In a way, that is even good practice, considering that many HPC users
do not always have access to the latest version of R, and that Travis is
making this fairly easy.
Now, with regard to your latest reply
Hello Kevin,
Well, bioc-devel packages are tested against bioc-devel (and R-3.5) in any
case. What I'm saying is that aside from testing the package against
bioc-devel, I can as well test against bioc-release too on my own. If the
package doesn't work with bioc-devel it shouldn't pass bioc-devel c
Dear Alexey,
The reason is somewhat implicitly given at
https://www.bioconductor.org/developers/how-to/useDevel/ :
"Package authors should develop against the version of *R* that will be
available to users when the *Bioconductor* devel branch becomes the
*Bioconductor* release branch."
In other w
Dear Bioconducotr community,
I wonder, what is the reason behind requirement for dependency R >= 3.5
(currently) for new packages?
As a developer I really want an installation of my package to be as easy as
possible and want my package to be easily installed from github. So
currently, when I deve
10 matches
Mail list logo
