Re: [R-pkg-devel] Keeping secrets in R packages

2015-06-05 Thread Imanuel Costigan 
Have you checked out Hadley's secret package?


https://github.com/hadley/secure/blob/master/README.md


Sent from my iPhone

On 6 Jun 2015, at 8:19 am, Neal Fultz  wrote:

I am working on updating the RGoogleDocs package to use OAuth2, since the
old api was recently turned off (at my job we use it as a poor mans
database).

As part of the auth process, I need to send google a client key and secret
in order to gain access to a spreadsheet. Is there a 'safe' place to store
the secret?
I would strongly prefer not requiring my end users to have to sign up for
their own google API keys, but I also do not want to store the secret in
the clear.

Any suggestions on best practices?

-Neal Fultz

   [[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

[R-pkg-devel] Calls to exported dplyr functions from DBI/dplyr backend

2016-01-08 Thread Imanuel Costigan 
Hi 

I am looking to release an updated version of RSQLServer and noticed that when 
checking the package, I was getting a large number of errors of the style:

* checking R code for possible problems ... NOTE
auto_copy: no visible global function definition for ‘same_src’
b

I have dplyr in Description > Imports and call dplyr functions such as 
`same_src` without them being imported into my package’s NAMESPACE (or making 
qualified calls using `::`, the latter being my usual preference). My thinking 
is that my package’s (dplyr) backend functionality should fail if dplyr itself 
is not attached on the search path (by for e.g. calling `library(dplyr)`). I 
think the latter is the behaviour that Hadley has advocated elsewhere (I can’t 
find reference in places I would expect).

I am looking for guidance on what to do in this circumstance. I see at least 
two possibilities:

* I import all these dplyr functions into my package (or call with ::) and make 
CRAN errors go away
* I stick with behaviour described above and risk wasting CRAN maintainers' 
time and have package rejected.

Many thanks
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] Open Source Survey, conducted by GitHub

2017-04-22 Thread Imanuel Costigan 
Thanks Jenny. I’m looking forward to seeing the results and the inevitable R 
package wrapper.

Imanuel
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

[R-pkg-devel] Odd R CMD build behaviour on Windows

2018-12-27 Thread Imanuel Costigan 
Hi all

[Originally posted on R-help which is probably not the right place - hence no 
response?]

I am finding that on Windows 10:

* the archive file produced by R (i386) CMD build command saves the resulting 
archive file in the present working directory 
* ...BUT the archive produced by the R (x64) CMD build command is **not** saved 
in the present working directory. Instead it is saved in the file path produced 
by `paste0(Sys.getenv("HOMEDRIVE"), Sys.getenv("HOMEPATH"))` or 
`Sys.getenv("HOMESHARE")` (the former resolves to H:\ which is an alias for the 
latter). This path is not represented in any other environment variables 
returned by Sys.getenv()

This behaviour persists for R-3.5.1 (formally release) and R-3.4.4. It also 
persists after I uninstall R and Rtools and then clean reinstall R-3.4.4 and 
R-3.5.1.

Has anyone else had this issue? Or tips on what might be causing this? 
Alternatively a pointer to the part of the R source code that determines the 
output directory for R CMD build would be much appreciated. 

I am running these commands in Powershell using the following commands:

Thanks.

```
& 'C:\R\R-3.5.1\bin\x64\R.exe' --no-site-file --no-environ --no-save 
--no-restore --quiet CMD build "C:\users\\Coding\testpackage\" 
--no-resave-data --no-manual

# Archive is **not** saved in present working directory, but saved to H:\

& 'C:\R\R-3.5.1\bin\i386\R.exe' --no-site-file --no-environ --no-save 
--no-restore --quiet CMD build "C:\users\\Coding\testpackage\" 
--no-resave-data --no-manual

# Archive is saved in present working directory.
```
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel