Updating r packages4/26/2023 Why would you want to do something that is painful more often? Because it leads to less pain overall. Recall that our preferred way to do this is via devtools::check() ( Section 5.6). In the current context, interpret this to mean that you should be running R CMD check regularly, preferably on multiple platforms, and promptly addressing any issues that surface. The main concerns are fairly timeless and we’ll use this checklist to help structure this chapter.īut first: note that you will have deep regrets if you approach preparing your package for CRAN as a separate activity that you do after completing the planned development for a release. This checklist is constantly-evolving and is responsive to a few characteristics of the package, so don’t be shocked if you see something a bit different than what we show here. The most concrete expression of our release process is the checklist produced by usethis::use_release_issue(), which opens a GitHub issue containing a list of todo’s. In this chapter, we focus on the actual process of releasing a package to CRAN, for the first time or as an update. We’ve been calling out CRAN-specific concerns throughout the book, on our journey through the various parts of a package, such as tests and examples. This chapter should be readable but is currently undergoing final polishing. You are reading the work-in-progress second edition of R Packages.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |