Re: [R-pkg-devel] R-devel cannot install my package

2022-09-27 Thread Tomas Kalibera
On 9/28/22 00:50, Bailey, Paul wrote: Hi, I'm trying to update WeMix on CRAN and when I use R-devel (2022-09-26 r82921 ucrt) to R CMD check --as-cran R-devel will not install the package. This is the log file [snip] ** testing if installed package can be loaded from temporary location *** arc

Re: [R-pkg-devel] Inquiry

2022-09-27 Thread Jeff Newmiller
If you haven't settled on exactly which approach you want to use in accomplishing the main goals of your exported package functions, then hiding the gory details can make it easier to tell people later to sod off when you decide those gory details functions should act different or use different

Re: [R-pkg-devel] Inquiry

2022-09-27 Thread Rolf Turner
On Tue, 27 Sep 2022 07:43:03 + Georgi Boshnakov wrote: > >...functions, that are not meant to be called directly by users, > >should be documented in a file named -internal.Rd. > > This is one option, convenient in the use-case of the question. But > why export a function that you active

[R-pkg-devel] R-devel cannot install my package

2022-09-27 Thread Bailey, Paul
Hi, I'm trying to update WeMix on CRAN and when I use R-devel (2022-09-26 r82921 ucrt) to R CMD check --as-cran R-devel will not install the package. This is the log file [snip] ** testing if installed package can be loaded from temporary location *** arch - i386 Error in .makeMessage(..., doma

Re: [R-pkg-devel] Inquiry

2022-09-27 Thread Georgi Boshnakov
>...functions, that are not meant to be called directly by users, should be >documented in a file named -internal.Rd. This is one option, convenient in the use-case of the question. But why export a function that you actively don't want the users to know about? There are cases when this is need