You might try using MRAN snapshots: https://mran.revolutionanalytics.com/documents/rro/reproducibility#standard <https://mran.revolutionanalytics.com/documents/rro/reproducibility#standard>
For example: https://cran.microsoft.com/snapshot/2018-01-01/src/contrib/yaml_2.1.16.tar.gz <https://cran.microsoft.com/snapshot/2018-01-01/src/contrib/yaml_2.1.16.tar.gz> ----- Zhian N. Kamvar, Ph. D. Postdoctoral Researcher (Everhart Lab) Department of Plant Pathology University of Nebraska-Lincoln ORCID: 0000-0003-1458-7108 > On Mar 8, 2018, at 14:39 , Jonathon Love <j...@thon.cc> wrote: > > hi, > > i'm bundling some R packages to go into a flatpak/flathub application. for > that it is necessary to provide the download URLs for all the required > dependencies in advance - including R packages. this works, *except* when an > R package version transitions from being the current version, to being > archived. > > the current version will be, say: > > https://cran.r-project.org/src/contrib/yaml_2.1.16.tar.gz > > then when yaml 2.1.17 comes out (which it just has), that url will return a > 404, and has become: > > https://cran.r-project.org/src/contrib/Archive/yaml/yaml_2.1.16.tar.gz > > this means everything breaks when a new version of an R package comes out. > > does anyone know if a stable url exists for R packages? > > with thanks > > jonathon > > ______________________________________________ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel
signature.asc
Description: Message signed with OpenPGP
______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
