packrat files to commit to svn repo to build Rmd
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
I am new to packrat (0.4.8-1) and TortoiseSVN (1.9.7). My goal is to push my project files (Rmd and css) to my svn repo, along with a snapshot of the package versions used throughout my code. My organization then uses Anthill Pro to automate the report build process and deploy to server. I need to make sure my projects can be built without needing to install packages on the server.
I am unsure which packrat files need to be committed to my svn repo to ensure a clean build process. After running packrat::init(), a packrat folder was created with subfolders lib, lib-ext, lib-R, src, init.R, packrat.lock, and packrat.opts. I also created a bundle, which appears in the bundles subfolder.
Which packrat files do I need to commit to ensure all of my required packages are available for building an Rmd docement?
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 reviewing the issue's packrat::init() setup and the listed packrat directory contents: lib, lib-ext, lib-R, src, init.R, packrat.lock, packrat.opts, and bundles. Check the repository's existing documentation or examples for guidance on committing a packrat project for automated R Markdown builds; done means documenting which files are required and how to reproduce the build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100