packrat follow folder symlinks
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
I had a symlink directory in my project folder and packrat was getting all packages that were in the symlink. Not necessarily an issue but maybe (if possible) adding a warning before proceeding may be a good idea as this may have unintended consequences.
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 reproducing packrat's behavior with a project directory containing a symlink to another folder, then identify where dependencies are collected. Determine the intended handling of directory symlinks and define done as either warning before following them or documenting the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100