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)

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