Re: [R-pkg-devel] R-devel warning: You used a knitr feature that depends on the digest package.

On Wed, 7 Feb 2018, Martin Maechler wrote: Gábor Csárdi on Tue, 6 Feb 2018 19:26:55 -0800 writes: > codetools is a recommended package, and it is part of most R > installations. builder.r-hub.io is a bit more strict, it does have the > recommended

Re: [R-pkg-devel] Depreciate Function

Hi Rami, I think you're confusing two things: 1) the warning a user receives when they use a deprecated function, and 2) the warning you receive when you (or CRAN) run R CMD check. 1) This is the correct behaviour: you want to warn your users that if they don't change their code, it may

Re: [R-pkg-devel] Depreciate Function

If the calls to your deprecated function can be replaced by calls to the new function - just do that. In this way users will not be tempted to use the deprecated function. If that is difficult, you can put a print statement in your old function telling the users whatever you want. But this may

Re: [R-pkg-devel] Depreciate Function

I follow the example of the R Packages book about depreciating a function which can be find here: http://r-pkgs.had.co.nz/release.html Is there another method to rename a function name? maybe to print message without triggering warning? Thanks! On Wed, Feb 7, 2018 at 1:36 PM, Maxime Turgeon <

Re: [R-pkg-devel] Depreciate Function

Hi Rami, Is there a reason for still using the deprecated functions in your examples? Because that's what's triggering the warnings. Best, Max From: R-package-devel on behalf of Rami Krispin

Re: [R-pkg-devel] Depreciate Function

Not sure where you get the warning. I guess only at places where you still use the old variant? Best, Uwe Ligges On 07.02.2018 16:38, Rami Krispin wrote: Hello all, I am trying to depreciate functions and replace them with a different function in the new version of the package, using the

[R-pkg-devel] Depreciate Function

Hello all, I am trying to depreciate functions and replace them with a different function in the new version of the package, using the Depreciate function which triggers warnings during the package submission to CRAN. For example, I am replacing the function seasonal_ly with the function

Re: [R-pkg-devel] Using C++11 and compilation in sub-directories together

On Wed, 2018-02-07 at 15:17 +0300, Alexander Loboda wrote: > Dear all, > > I'm trying to build a package that uses c++11 code and sub-directories > in src/ according to the "Writing R Extensions" manual, but it seems > like R CMD doesn't want to compile the code with c++11 flags when source >

Re: [R-pkg-devel] Fwd: [CRAN-pretest-archived] CRAN submission huxtable 2.0.2

Hi Dirk Not running the test on CRAN would fix the problem, but it is kind of an admission of failure. Part of CRAN's point is quality control, so switching off tests just to pass seems perverse. I'll do it if that is the only option. Yes, I bet the CRAN guys are highly busy, and full respect to

Re: [R-pkg-devel] Fwd: [CRAN-pretest-archived] CRAN submission huxtable 2.0.2

On 7 February 2018 at 11:53, David Hugh-Jones wrote: | Hi guys, | | I've been having some problems with updating my 'huxtable' package on CRAN. | The latest issue is that I run a test which renders a rmarkdown document to | PDF, using rmarkdown::render. This passes R CMD check fine on my

[R-pkg-devel] Fwd: [CRAN-pretest-archived] CRAN submission huxtable 2.0.2

Hi guys, I've been having some problems with updating my 'huxtable' package on CRAN. The latest issue is that I run a test which renders a rmarkdown document to PDF, using rmarkdown::render. This passes R CMD check fine on my machine, on travis and on win-builder, but fails on the CRAN machines

Re: [R-pkg-devel] New CRAN package assistance

On 7 February 2018 at 21:54, Huw Campbell wrote: | I have just submitted a package for CRAN which works on my Mac and linux | boxes, but there are notes for Windows and my license file. There is little | indication as to what the actual problems are. | | The library is a simple binding for the

[R-pkg-devel] Package removed due to dependency error (but dependency not removed)

Hi all I have a couple of packages that depend on a third package (seewave ). My packages were removed from CRAN because an issue with this dependency: seewave produces an error when installed in r-release-osx-x86_64

[R-pkg-devel] New CRAN package assistance

Hey all, I have just submitted a package for CRAN which works on my Mac and linux boxes, but there are notes for Windows and my license file. There is little indication as to what the actual problems are. The library is a simple binding for the snappy compression library. I have been rather