Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What are the steps in submitting an R-package to CRAN and how long does each step take? [closed]

Tags:

r

cran

I have noticed that once submitted to incoming (ftp://cran.r-project.org/incoming) the package name receives the following suffixes .save, .pending and .noemail. Then, the package disappears from incoming. I suppose the next step is that the CRAN maintainers put it on the main server (http://cran.r-project.org/src/contrib/ http://cran.r-project.org/web/packages/) and then it gets propagated to the mirrors.

My questions:

(1)Could someone confirm the steps and provide detail on them. Especially what happens after the package disappears from incoming (didn't find a way to check status for that step)

(2) how long does each step take on average?

Thanks!

like image 743
user1134616 Avatar asked Dec 21 '12 23:12

user1134616


People also ask

Why should I submit my R package to Cran?

If you want your package to have significant traction in the R community, you need to submit it to CRAN. Submitting to CRAN is a lot more work than just providing a version on github, but the vast majority of R users do not install packages from github, because CRAN provides discoverability, ease of installation and a stamp of authenticity.

How do I release a package to Cran?

To get your package ready to release, follow these steps: Pick a version number. Run and document R CMD check. Check that you’re aligned with CRAN policies. Submit the package to CRAN. Prepare for the next version by updating version numbers. Publicise the new version.

How many packages are there on CRAN and GitHub?

[^1] As of writing this post, there are more than 16,0000 packages on CRAN, and around 85,000 packages on GitHub. This can be overwhelming, especially when trying to find the package for your specific problem or when trying to learn what others are doing.

What is the difference between releasing on CRAN and using R?

Both offer the ability for others to use your package but differ in several important aspects. Releasing on CRAN offers additional tests that ensure that your package is stable across multiple operating systems and is easily installable with the function in R.


1 Answers

All the public info about CRAN policies is here:

http://cran.r-project.org/web/packages/policies.html

if the info you seek is not there, then only the Gods of CRAN know it. I wouldn't rely on those suffixes having any great meaning to us. That would be CRAN's internal processing, which might change at the whims of the Gods of CRAN.

The answer to question 2 is the same answer to 'how long is a piece of string?'.

like image 170
Spacedman Avatar answered Oct 07 '22 21:10

Spacedman