A) You cannot assume the package code will have write access to the library directories. The user/admin who installs the package may never load the package.
B) Downloading binary files for execution without the direct involvement of the user/admin is a security risk. C) Open-source package license means the source code is part of the package. Downloading binaries later fails this requirement. On July 1, 2019 10:03:07 PM PDT, Jialin Ma <marl...@gmx.cn> wrote: >Hi everyone, > >Currently my package has a script downloading additional DLLs >into "inst/libs" and being called in "Makevars.win". In this way these >DLLs get copied to libs when installing the package and I am able to >load them with "library.dynam". > >However R CMD check gives the following warning. > > * checking package subdirectories ... WARNING > Found the following non-empty subdirectories of 'inst' also used by R: > inst/libs > It is recommended not to interfere with package subdirectories used by > R. > >I was wondering what would be the best practice for my case, or I am >safe >to ignore this warning (suppose I am planing for a CRAN submission). > >I know many packages will download static library and link them at >compile >time. But I haven't see any example with additional DLL files. > >Thanks. >Jialin Ma > >______________________________________________ >R-package-devel@r-project.org mailing list >https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sent from my phone. Please excuse my brevity. ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
