Should I (git) ignore my cedar cache?

In a vein similar to this question : I am writing a package and using knitr to write several documents in inst/doc/ . Since I use github to host my repo (and I intend to point people to this repo to get the package), I wonder if I should be the version that controls my caches of different documents.

I ask this question because it is not clear when the cache falls into the guidelines provided by this other question (which addresses when certain types of files should and should not be in the .gitignore repo).

Can anyone shed some light on how package handlers using knitr and git process their caches?

+6
source share
1 answer

If the R CMD check passes without a cache cedar, and I think it would be, I would not include them. In fact, I suspect that the R CMD check will give a note on the cache files present in the package. I know that for LaTeX files you want to include the .tex file in the R package and in the version control. Other necessary files should be automatically generated during installation.

+1
source

All Articles