1800 PACKRAT DRIVER APP LOGIN INSTALL

Any guidance on configuring my repo so packrat can understand it would be great. I think this last part is showing I'm materially misunderstanding something. At no point would a repo have the structure it's looking for? I would have thought this is guaranteed to fail, because repos follow the C://bin/windows/contrib/3.3/ structure. If I drill into packrat:::findLocalRepoForPkg, it fails because it can't find a file/folder called: 'C://'. If I follow through the functions, I can see the particular point of failure is packrat:::findLocalRepoForPkg('

Options(repos = c(options('repos')$repos,LocalCurrent = paste0('file:',RepoAddress)))Ĭurrently this works nicely and I can install my custom package from the local repo. # Add this new repo to Rs knowledge of repos. I understand the only way I can get our custom packages to work within apps with RSConnect is to get up a local repo and set our options(repos) to include this.Ĭurrently I have the following: library(drat)ĭrat::insertPackage(, repodir = RepoAddress) For our work, we have made custom packages, which we have updated amongst ourselves by opening the project and build+reloading.

We have recently got RStudio Connect in my office.

1800 PACKRAT DRIVER APP LOGIN INSTALL

1800 packrat driver app login