14h
revised The correct use of devtools and/or RStudio with respect to .Rbuildignore
deleted 9 characters in body
15h
asked The correct use of devtools and/or RStudio with respect to .Rbuildignore
20h
asked Using aliases in combination with @inheritedParams (package roxygen2)
Aug
19
comment How to make devtools::test() consider package dependencies
Okay, got it. But just to make sure: there's no "built-in shortcut method" of devtools (or roxygen2) that would simply make sure that Depends and Imports entries in DESCRIPTION are transferred to NAMESPACE, right?
Aug
19
comment How to make devtools::test() consider package dependencies
Duh... forgot to explicitly install roxygen2. Sorry guys.
Aug
19
revised How to make devtools::test() consider package dependencies
added 124 characters in body
Aug
19
comment How to make devtools::test() consider package dependencies
@Andrie: didn't find that setting (see screenshot above). Also: what would I need to do when not using RStudio. Running roxygenize() prior to unit testing?
Aug
19
comment How to make devtools::test() consider package dependencies
Ad 1): no, didn't do that yet. I thought stating a "global" dependency in the DESCRIPTION file would be enough (even though or more fine-tuned dependency management might indeed make sense). Ad 2) the package is about an alternative way of doing what utils::packageDependency() does but when you want to read the DEPENDENCY info based on a file path. So I need it for the actual unit tests (e.g. when using the equivalent of the fields argument of utils::packageDependency(). So my bad: this indeed has nothing to do with the tests failing.
Aug
19
revised How to make devtools::test() consider package dependencies
added 8 characters in body
Aug
19
revised How to make devtools::test() consider package dependencies
added 8 characters in body
Aug
19
comment How to make devtools::test() consider package dependencies
Wait, now I'm confused. I checked the NAMESPACE file after building the package with devtools::build(), but the only thing in there is exportPattern("^[[:alpha:]]+"). I thought that either one of devtools or roxygen2 takes care of populating the NAMESPACE file? Also: I thought maybe it's not working due to the fact that I only had a copy of DESCRIPTION in ./tests/testthat, but no copy of NAMESPACE. But after making sure both copies are there, my unit tests still fail.
Aug
19
comment How to make devtools::test() consider package dependencies
Aha! Good point. While still at dev-mode, what's the best way to have devtools "build" the NAMESPACE file? Should I run devtools::build() everytime before running my unit tests? And with respect to the DESCRIPTION file: sure, I'm just hacking away at this point ;-)
Aug
19
asked How to make devtools::test() consider package dependencies
Aug
3
awarded Nice Question
Jul
30
comment Compiling RCurl from source on Windows
Cool, thanks for the update and the kind words on github! Are you running on windows and managed to compile from source? It'd be very interested in the details with respect to libcurl etc.!
Jul
29
comment Compiling RCurl from source on Windows
Well, there are binaries until v1.95.4.2, but that's not working for me (has to do with this issue). Thanks, though!
Jul
29
comment Compiling RCurl from source on Windows
Thanks, but it seems to me simply installing or putting it somewhere on my machine won't really help as the package seems to be pretty rigid on where it looks for the DLLs. Also, I didn't find the files libcurl-4.dll and libz.dll in the bundle you mentioned. Any ideas?
Jul
29
asked Compiling RCurl from source on Windows
Jul
29
revised R: Pass by reference
added 44 characters in body
Jul
27
revised Dynamic user home directory on Windows (changing %HOMEDRIVE% and %HOMEPATH%)
added 4 characters in body
1 2 3 4 5