And another 2 cents from me. A package is the basic unit of functionality in R. Whatever functionality you are providing, I think a package is the best way to deliver it. There is a well developed framework for versioning, dependency resolution, testing, and distribution.
If you choose some other mechanism, then I suspect that any developer problems you eliminate will just return as system administration problems. Martyn On Tue, 2014-04-08 at 10:12 +0200, Xavier Robin wrote: > My 2 cents... > > On 07/04/14 10:12, Romain François wrote: > > It would also mean many copies of the same code base. To which I’m > > thinking: so what. > No, it will mean many copies of /many different and mostly outdated/ > code bases. > You can count on me to forget to git pull next time I update my package. > > What about something like the BH package that contains the boost > headers? I'm using it in a project I'm working on, and just use a > LinkingTo declaration with something in Makevars. > Of course ideally it would be in a build-depends type of declaration so > it isn't pulled during binary installs. > > Xavier > > _______________________________________________ > Rcpp-devel mailing list > Rcpp-devel@lists.r-forge.r-project.org > https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel _______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel