|
Andreas,
This is extremely helpful! Thank you so much. I've had a chance to work with some of the tools you described, and I do have a couple of quick questions:
| The preparation of R packages is very simple. Just install the dh-r
package (at best from unstable/sid) and do
| | prepare_missing_cran_package lomb | prepare_missing_cran_package ... | | This will create close to ready packaging repositories in | | ../CRAN_prospective | | from the said package as well as all its not yet packaged dependencies. Please verivy the "FIXME" inside debian/copyright and also make sure the description in debian/control makes sense. Once you have created such repositories there is some helper script I have run the function you described and noticed that it performed similarly to the dh-make-R command I was using previously. Is this command invoking prepare_missing_cran_package at some point? Is this an acceptable way to discover and package dependencies? Also, I have noticed that this process creates two directories in the ../CRAN_prospective directory for each dependency. One is named simply after the dependency (e.g. "lomb") while the other seems to be named using the debian standard
for R packages (e.g. "r-cran-lomb"). Adding to my confusion, the directory the simpler name contains what I would expect to be standard for building a debian package (i.e. the debian directory along with the usual R package structure), but the other directory
only contains a .git directory. What is the rationale behind the creation of both of these directories? My inclination is to only use the one with the created debian directory and ignore the other, but I am concerned by the presence of this second directory.
Am I meant to combine the directories somehow before running the script to push the repository to salsa? My brief read-through of the script you sent me seems to indicate that this is the case. (Though admittedly, I'm a bit of a novice when it comes to bash
scripting, so I may be missing something)
Thanks again for all your help. It means a lot to me. I feel like I'm making real progress now on this project, and it's very exciting!
Ben
|