[R] How to publish a new package on CRAN
bgunter@4567 @end|ng |rom gm@||@com
Wed May 15 16:48:43 CEST 2019
This appears to be off topic here, but, when expanded, might make a nice
post on the R-bloggers site.
On Wed, May 15, 2019 at 6:10 AM J C Nash <profjcnash using gmail.com> wrote:
> In reading the original post, I could not help but get a feeling that the
> writers were
> going through an exercise in learning how to put a package on CRAN. Having
> organized "Navigating
> the R Package Universe" at UseR!2017, where Spencer Graves, Julia Silge
> and I pointed out the
> difficulties for users in finding appropriate tools among the thousands of
> packages, perhaps
> an effort to organize or modify EXISTING packages would be more useful.
> It is NOT that new packages are unwelcome per se, but that we continue to
> need organization and
> amalgamation of these new packages into collections or categories so that
> similar functionality
> can be accessed more efficiently. And as a retired academic, I know how
> much "new" is valued over
> "review and assessment" of existing material. I've found several "new"
> publications of codes I
> published nearly half a century ago in the literature from time to time.
> Maybe the posters could
> write RPlagiarizedCheck.
> On 2019-05-14 10:31 p.m., Abby Spurdle wrote:
> > And there's the R Manuals:
> > https://cran.r-project.org/manuals.html
> > The most relevant one (for this purpose) is "Writing R Extensions".
> > [[alternative HTML version deleted]]
> > ______________________________________________
> > R-help using r-project.org mailing list -- To UNSUBSCRIBE and more, see
> > https://stat.ethz.ch/mailman/listinfo/r-help
> > PLEASE do read the posting guide
> > and provide commented, minimal, self-contained, reproducible code.
> R-help using r-project.org mailing list -- To UNSUBSCRIBE and more, see
> PLEASE do read the posting guide
> and provide commented, minimal, self-contained, reproducible code.
[[alternative HTML version deleted]]
More information about the R-help