Allow specification of a list of packages rather than searching through R files
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
On a more complicated setup where packrat is being used to maintain a number of machines using a large codebase with many R files, one may wish to just specify a list of packages for packrat to maintain rather than have packrat search through all R files to make that list. Allowing this list specification would:
- stop packrat from managing packages undesired on all machines
- allow one to tell packrat to manage packages not explicitly referenced in R files
On a large codebase being used on multiple machines, a package list specification option would be very useful in preference to the current search functionality.
Thank you again for all your hard work! Very grateful.
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 current package-discovery entry point that searches R files and the existing packrat configuration. Define how a user-specified package list is represented and processed; done means packrat can manage explicitly listed packages without relying on the repository-wide R-file search, including packages not referenced in those files.
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
- 45/100