For the same reason, handling false positive in CRAN checks, there are
other places that could be improved.
Like "size of tarball" NOTE.
If one could control this size with an environment variable. Similarly
to the proposal made by Jim. It would be useful as well.
On Thu, Apr 16, 2020 at 5:06 PM H
I'd second Jim's feature request - it would be useful to be able to
disable this in CI and elsewhere.The concept of using an "unusual"
version component such as a very large number does a nice job of
indicating "unusual" and serves as a blocker for submitting
work-in-progress to CRAN by mistake
Or you use a fourth component to signal a development version as Rcpp has
done for years (and, IIRC, for longer than devtools et al used '9000').
There is no functional difference between 1.2.3.1 and 1.2.3.9000. They are
both larger than 1.2.3 (in the package_version() sense) and signal an
inter
If you test a package with `R CMD check --as-cran` one of the
'incoming' checks is for a large version number, it gives a NOTE like
this
* checking CRAN incoming feasibility ... NOTE
Maintainer: ‘Jim Hester ’
Version contains large components (0.0.0.9000)
This is a useful check when
