R devel - Jan 2017 - cross-platform portable code in CRAN Repository Policy

On 27 January 2017 at 21:54, G?bor Cs?rdi wrote:
| On Fri, Jan 27, 2017 at 9:28 PM, Da Zheng <zhengda1936 at gmail.com>
wrote:
| > What major R platforms does this policy refer to?
| >
| 
| Linux, macOS, Windows.
| 
| 
| > Currently, my package runs in Ubuntu. If it works on both Ubuntu and
| > Redhat, does it count as two platforms?
| >
| 
| I think that Linux is just one. Is it hard to make it work on macOS?
| 
| I am not saying that if it is Linux-only then it definitely cannot make it
| to CRAN.
| A CRAN maintainer will decide that.

Gabor is *way* too modest here to not mention the *fabulous* tool he has
written (with the [financial] support of the R Consortium):  R Hub.

These days I just do    'rhub::check_for_cran()'   and four tests launch
covering the three required OSs as well as the required r-devel and r-release
versions.  Results tickle in within minutes by mail; the windows one (which
is slowest) is also display.  You need a one-time token handshake.

I strongly recommend the service.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

Second this.  As the CRAN Policies suggests, there's also the very
handy winbuilder service (https://win-builder.r-project.org/) you can
use to check your package on Windows.  This service has been a
valuable workhorse for years.

We should also mention the continuous integration (CI) services
provided for free by Travis (Linux and macOS) and AppVeyor (Windows)
in combination with GitHub (or GitLab, ...).  By adding simple
.travis.yml and appveyor.yml to your Git repos (e.g.
https://github.com/HenrikBengtsson/globals), they run R CMD check
--as-cran and covr::package_coverage() etc for you more or less on the
fly, e.g.

* https://travis-ci.org/HenrikBengtsson/globals
* https://ci.appveyor.com/project/HenrikBengtsson/globals

/Henrik

PS. Thanks to everyone who made all of the above possible.

On Fri, Jan 27, 2017 at 2:17 PM, Dirk Eddelbuettel <edd at debian.org>
wrote:
>
> On 27 January 2017 at 21:54, G?bor Cs?rdi wrote:
> | On Fri, Jan 27, 2017 at 9:28 PM, Da Zheng <zhengda1936 at
gmail.com> wrote:
> | > What major R platforms does this policy refer to?
> | >
> |
> | Linux, macOS, Windows.
> |
> |
> | > Currently, my package runs in Ubuntu. If it works on both Ubuntu and
> | > Redhat, does it count as two platforms?
> | >
> |
> | I think that Linux is just one. Is it hard to make it work on macOS?
> |
> | I am not saying that if it is Linux-only then it definitely cannot make
it
> | to CRAN.
> | A CRAN maintainer will decide that.
>
> Gabor is *way* too modest here to not mention the *fabulous* tool he has
> written (with the [financial] support of the R Consortium):  R Hub.
>
> These days I just do    'rhub::check_for_cran()'   and four tests
launch
> covering the three required OSs as well as the required r-devel and
r-release
> versions.  Results tickle in within minutes by mail; the windows one (which
> is slowest) is also display.  You need a one-time token handshake.
>
> I strongly recommend the service.
>
> Dirk
>
> --
> http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

Thank you very much for all your responses. It's very clear to me what I
need to do and what service I should use for testing now.

Thanks,
Da

On Fri, Jan 27, 2017 at 5:40 PM, Henrik Bengtsson <
henrik.bengtsson at gmail.com> wrote:
> Second this.  As the CRAN Policies suggests, there's also the very
> handy winbuilder service (https://win-builder.r-project.org/) you can
> use to check your package on Windows.  This service has been a
> valuable workhorse for years.
>
> We should also mention the continuous integration (CI) services
> provided for free by Travis (Linux and macOS) and AppVeyor (Windows)
> in combination with GitHub (or GitLab, ...).  By adding simple
> .travis.yml and appveyor.yml to your Git repos (e.g.
> https://github.com/HenrikBengtsson/globals), they run R CMD check
> --as-cran and covr::package_coverage() etc for you more or less on the
> fly, e.g.
>
> * https://travis-ci.org/HenrikBengtsson/globals
> * https://ci.appveyor.com/project/HenrikBengtsson/globals
>
> /Henrik
>
> PS. Thanks to everyone who made all of the above possible.
>
> On Fri, Jan 27, 2017 at 2:17 PM, Dirk Eddelbuettel <edd at
debian.org> wrote:
> >
> > On 27 January 2017 at 21:54, G?bor Cs?rdi wrote:
> > | On Fri, Jan 27, 2017 at 9:28 PM, Da Zheng <zhengda1936 at
gmail.com>
> wrote:
> > | > What major R platforms does this policy refer to?
> > | >
> > |
> > | Linux, macOS, Windows.
> > |
> > |
> > | > Currently, my package runs in Ubuntu. If it works on both
Ubuntu and
> > | > Redhat, does it count as two platforms?
> > | >
> > |
> > | I think that Linux is just one. Is it hard to make it work on macOS?
> > |
> > | I am not saying that if it is Linux-only then it definitely cannot
> make it
> > | to CRAN.
> > | A CRAN maintainer will decide that.
> >
> > Gabor is *way* too modest here to not mention the *fabulous* tool he
has
> > written (with the [financial] support of the R Consortium):  R Hub.
> >
> > These days I just do    'rhub::check_for_cran()'   and four
tests launch
> > covering the three required OSs as well as the required r-devel and
> r-release
> > versions.  Results tickle in within minutes by mail; the windows one
> (which
> > is slowest) is also display.  You need a one-time token handshake.
> >
> > I strongly recommend the service.
> >
> > Dirk
> >
> > --
> > http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
> >
> > ______________________________________________
> > R-devel at r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-devel
>
	[[alternative HTML version deleted]]