CRAN

After the previous post collecting information about repositories I want to collect here my thoughts on adding a package in a repository and how repositories are recognized. As in the previous post this is built on the assumption that one already has a package or more and wants to distribute it.

This is a brief announcement of rtweet version 2.0.0. This major version changes signals the move from the API v1.1 to the API v2. There haven’t been many changes since 1.

First time successful submissions

In this post I want to collect some thoughts about R repositories. In R we have multiple repositories that store packages for users. In this post I want to write about the purpose, functionality, benefits and drawbacks of R repositories and how packages are managed.

Some analysis on the RCurl and XML dependencies.

A short presentation in Spanish about submitting a package to CRAN and maintain it.

Introduction In the first post of the series we briefly explored packages available on CRAN. Now I’ll focus on history of the packages and its size using the following files:

Exploration of the CRAN archive: First part about packages published on CRAN

Most frequent reason is due to the package not fixed on time, followed by depending on packages archived and policy violation.

Description of the submission process to CRAN