> > Below is what I've found so far, (before getting tired of licensing > > issues) > > > > Any thoughts about how to handle this? > > I wonder how this was dealt with before? If that much data sets were > needed to build the docs, how did the doc generation process worked > before?
Perhaps the earlier packages weren't built using a tool that disables network access? the get_rdataset function will attempt to download the file first. Although it hurts reproducibility, that is certainly a simpler solution. > > BTW, I'd love if you would merge your work to master branch. I'm a > bit > confused by the amount of branches and lost track which one to look > at. I verified which was which and deleted the obsolete branch. use detrout-python3-try2 (the only detrout branch that should be left) > > > The files are being downloaded from this github repository. > > > > https://github.com/vincentarelbundock/Rdatasets a useful index of > > the > > datasets is > > http://vincentarelbundock.github.com/Rdatasets/datasets.html > > This reminds me to the debian/README.source files ftpmaster once > suggested for R packages[1]. May be that's an apropriate way to > document the licenses? Feel free to find examples for instance > in the package r-cran-ape. I really wish that listing the citation for these early scientific datasets counted as complying with the license. Diane
