From j@me@@|@he@ter @end|ng |rom gm@||@com  Mon Mar  4 13:59:57 2019
From: j@me@@|@he@ter @end|ng |rom gm@||@com (Jim Hester)
Date: Mon, 4 Mar 2019 07:59:57 -0500
Subject: [Rd] Package inclusion in R core implementation
In-Reply-To: <CAL0QV_Pgbif3=Hf1sw-O7Fy685N9upyYPyUK7c7FhgUd6yLMjg@mail.gmail.com>
References: <CAL0QV_MRORtsqzXbbY69-v2CUEy8Nmd6gk3VJPBvSt=sa=v8uQ@mail.gmail.com>
 <CAL0QV_Pgbif3=Hf1sw-O7Fy685N9upyYPyUK7c7FhgUd6yLMjg@mail.gmail.com>
Message-ID: <CAD6tx95tn82NE=TFAoaOyYxV1_QBgBSfLzNSWMa+nrL77C23gQ@mail.gmail.com>

Conversely, what is the process to remove a package from core R? It seems
to me some (many?) of the packages included are there more out of
historical accident rather than any technical need to be in the core
distribution. Having them as a core (or recommended) package makes them
harder update independently to R and makes testing, development and
contribution more cumbersome.

On Fri, Mar 1, 2019 at 4:35 AM Morgan Morgan <morgan.emailbox at gmail.com>
wrote:

> Hi,
>
> It sometimes happens that some packages get included to R like for example
> the parallel package.
>
> I was wondering if there is a process to decide whether or not to include a
> package in the core implementation of R?
>
> For example, why not include the Rcpp package, which became for a lot of
> user the main tool to extend R?
>
> What is our view on the (not so well known) dotCall64 package which is an
> interesting alternative for extending R?
>
> Thank you
> Best regards,
> Morgan
>
>         [[alternative HTML version deleted]]
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

	[[alternative HTML version deleted]]



[Rd] Package inclusion in R core implementation
Jim Hester