Re: [R-pkg-devel] Optional library dependencies for compiled code

2020-01-29 Thread Travers Ching
I'd like to add, for bundling `zstd` and `lz4`, I was told by Professor Ripley that I must first check for system installations and use that when possible, because of possible security issues being fixed in later updates. I think that's a good idea, and can be set up with a configure script: 1)

[R-pkg-devel] win-builder R-oldrelease downstream car

2020-01-29 Thread Mollie Brooks
Hi, The glmmTMB developers and I are having a hard time figuring out how to avoid some errors that only occur when we test our package on the R-oldrelease version on win-builder. I tried to replicate them locally on a Windows computer by installing R 3.5.3, but I could not. The error occurs

[R-pkg-devel] RES: Error after package update

2020-01-29 Thread Tiago Olivoto
Thanks, Gabor. The error occurred even when I restarted my section. I'm not sure if this was the solution, but I was using a development version of 'vctrs' (a package that 'tidyselect' depends on) After installing the stable version of 'vctrs' (v0.2.2) all worked well. Best regards, Tiago >

Re: [R-pkg-devel] Optional library dependencies for compiled code

2020-01-29 Thread Iñaki Ucar
On Wed, 29 Jan 2020 at 15:11, Guido Kraemer wrote: > > I am developing an R package that can make (optional, but strongly > recommended) use of a number of external compression algorithms. What is > the best strategy if I want to distribute this as an R package? Because > the package is for

Re: [R-pkg-devel] Optional library dependencies for compiled code

2020-01-29 Thread Jeff Newmiller
Complex system dependencies are not cleanly handled by the R packaging system, but Suggesting other packages is. You could create or re-use an existing package for each external dependency and possibly even let the user specify which one they want to your dependent package the way DBI handles

Re: [R-pkg-devel] Optional library dependencies for compiled code

2020-01-29 Thread Dirk Eddelbuettel
Guido, On 29 January 2020 at 15:11, Guido Kraemer wrote: | I am developing an R package that can make (optional, but strongly | recommended) use of a number of external compression algorithms. What is | the best strategy if I want to distribute this as an R package? Because It's actually a

[R-pkg-devel] Optional library dependencies for compiled code

2020-01-29 Thread Guido Kraemer
I am developing an R package that can make (optional, but strongly recommended) use of a number of external compression algorithms. What is the best strategy if I want to distribute this as an R package? Because the package is for reading large external data sets, the package will probably not

Re: [R-pkg-devel] Error after package update

2020-01-29 Thread Gábor Csárdi
Hi, I don't see this with dplyr 0.8.3 and tidyselect 1.0.0. Please make sure that you restart your R session after installing packages, otherwise the previous versions might be still loaded. One easy way to start a new R process is to use the reprex package to create a reproducible example. If

[R-pkg-devel] Error after package update

2020-01-29 Thread Tiago Olivoto
Hi everyone, After updating my R package list I just begin to get the following error with dplyr::select() A minimal reproducible example with iris dataset: --- library(dplyr) select(iris, Species) Erro: `...` is not empty. We detected these problematic