As of R 3.1.0 I get the following R check:
* checking package dependencies ... NOTE
No repository set, so cyclic dependency check skipped
I tried this advice: https://twitter.com/phylorich/status/431911660698083328
No go. I put the line options(repos="http://cran.rstudio.com/")
in a .Rprofile in the package root directory. Still get the Note.
Also section 1.3.1 of Writing R Extensions states:
Some Windows users may need to set environment variable R_WIN_NO_JUNCTIONS
to a non-empty value. The test of cyclic declarations33in DESCRIPTION
files needs repositories (including CRAN) set: do this in ~/.Rprofile.
Is this possibly a result of the set environment variable R_WIN_NO_JUNCTIONS
? If so how can I go about doing this? Any other possible causes of the note or suggested fixes?
The answer above only works for Linux. On Windows I had to use a different method. When I tried to build and check my new package in R 3.2.0 on Windows 7, I got the same error:
I tried creating a file .Rprofile in my new package's root directory, but that didn't work. Instead I had to go to:
and edit the file:
In the Rprofile.site file I added the suggested line:
After I edited the Rprofile.site file, the NOTE "No repository set, so cyclic dependency check skipped" finally disappeared.
From Writing R Extensions
The test of cyclic declarations in DESCRIPTION files needs repositories (including CRAN) set: do this in ~/.Rprofile, by e.g
Recommended
User should double check if his .Rprofile is in his home and that it contains the mentioned option.
Or from R session using extra package:
User should double check if the option entry is not nested in the IF condition, like in the following code:
Dry run for any platform
Here is R script preparing easy temporary case of R package for testing, helping to faster find what is going wrong in your local usage. This aproach helped myself to locate what was wrong in my .Rprofile file and generally can help to set up working initial state. In best case, the check run should show only 1 NOTE about new submission.
Example
If your .Rprofile does not exist it will be created and one new line placed at the end of file in any case.
The
makePackage.R
scriptChecking the package
There is user profile and site profile, in the approach above you bypasses site profile (in second step) by using
--no-site-file
option for package skeleton option.PDF errors
You can experience PDF and latex related errors, caused very likely by missing or not complete latex instalation. Ycan use
--no-manual
option to skip PDF tests.