[Rd] [R-SIG-Mac] check leads to .o files and to packagename-Ex.R
bbolker at gmail.com
Thu Jun 2 15:06:17 CEST 2011
On 06/02/2011 06:47 AM, Benilton Carvalho wrote:
> 'R CMD check' should be applied on the .tar.gz, not on the source directory.
Why? The help says: "Check R packages from package sources, which can
be directories or package 'tar' archives with extension '.tar.gz',
'.tar.bz2' or '.tgz'." I just skimmed through the relevant section
(1.3.1) in the R Extensions manual, and it doesn't say anything about
running on tarballs being preferred.
Add my vote to the wishlist that the src directory should get cleaned
after R CMD check.
> So, it'd be something like:
> R CMD build pkg
> R CMD check pkg_version.tar.gz
> On 2 June 2011 06:54, Marius Hofert <m_hofert at web.de> wrote:
>> Dear expeRts,
>> I work on the R package "nacopula" (https://r-forge.r-project.org/projects/nacopula/) under Mac OS X 10.6.7 (MacBook Pro). The session info is:
>> R version 2.14.0 Under development (unstable) (2011-05-02 r55730)
>> Platform: x86_64-apple-darwin9.8.0/x86_64 (64-bit)
>> When I apply "R CMD check nacopula" my source directory is filled with .o files (which leads to
>> a warning for the next check). Further, if I use R 2.14.0, the check produces a file "nacopula-Ex.R"
>> on the top level, i.e., where folders like R, src, tests, man, inst, and demo reside.
>> Shouldn't the source directory stay nice-and-clean, without being filled with .o
>> files and example files?
>> Attachment: screen shot
>> R-SIG-Mac mailing list
>> R-SIG-Mac at r-project.org
More information about the R-devel