packrat cache cannot cope with build-time cross-package object copies
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
knitr contains a reference to evaluate::evaluate. The signature of evaluate::evaluate has changed over time. A packrat-cached copy of knitr will err if built against evaluate-1.0 but using evaluate-0.9 at runtime.
https://github.com/yihui/knitr/issues/1441
Packages which contain these cross-package references can be fixed, but it would be good if the packrat cache could cope with this type of data.
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 with the packrat cache behavior around the knitr and evaluate cross-package reference described in the issue. Reproduce the mismatch by building against evaluate-1.0 and running with evaluate-0.9, then investigate how cached package objects are copied. Done means this scenario is handled without the cached knitr copy failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100