On Fri, Jul 26, 2019 at 8:46 AM Ben Bolker wrote:
>
>I'd add: as far as I know CRAN policy would only require you to
> report the minimum version if your package would fail on one of the
> older R versions that CRAN still tests (at present I think this goes
> back to 3.5.2). For regular packa
I'd add: as far as I know CRAN policy would only require you to
report the minimum version if your package would fail on one of the
older R versions that CRAN still tests (at present I think this goes
back to 3.5.2). For regular package developers (i.e. without the
resources of RStudio) it's a
I no longer believe this to be good advice - I think you should only
declare a specific dependency if you want to strongly assert that your
package works with those versions. For example, all tidyverse versions
depend on R 3.2 and later, because we test on all those versions.
Hadley
On Friday, Ju
Hello,
Numerous CRAN packages report minimum R versions within the Depends field
of the DESCRIPTION file.
Is this reporting always necessary?
Hadley Wickham's book "R Packages" states:
"You can also use Depends to require a specific version of R, e.g. Depends: R
(>= 3.0.1) . As with packages, i
