Use environment variables to find the packrat instance
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
I'm using Packrat along with other language-specific package managers (e.g., Pyenv for Python) in several projects. Packrat has this unique constraint however that it has to be installed in the very folder the project sit in; launching R from a sub-folder won't work since it relies on having a .Rprofile script calling Packrat.
I'd like to suggest instead to have library("packrat") first check for an optional environment variable that points to that folder, so that regardless of where your current working directory is you can still access your virtual environment--very much like Pyenv, Renv, Conda, Perlbrew and other package and environment managers.
Best, Aurélien
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the library("packrat") initialization and the .Rprofile behavior described in the issue. Trace how Packrat finds its project folder, then verify that an optional environment variable supports launching R from a sub-folder without changing existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100