Re: [R-pkg-devel] [External] Re: What is a "retired"package?

2021-09-21 Thread Viechtbauer, Wolfgang (SP)
:) That's a fortune nomination on my part. Best, Wolfgang >-Original Message- >From: R-package-devel [mailto:r-package-devel-boun...@r-project.org] On Behalf >Of >Hadley Wickham >Sent: Tuesday, 21 September, 2021 20:45 >To: Lenth, Russell V >Cc: r-package-devel@r-project.org >Subject:

Re: [R-pkg-devel] [External] Re: What is a "retired"package?

2021-09-21 Thread Hadley Wickham
Yes, as Lionel said that is why we have changed our terminology to superseded — we wanted to imply that a retired package was still a useful member of society, if not working full-time anymore, but most people seem to think that retired means that we took the package out behind the shed and put it

Re: [R-pkg-devel] [External] Re: What is a "retired"package?

2021-09-21 Thread Lenth, Russell V
Hadley, As I suspected, and a good point. But please note that the term "retired" causes angst, and it may be good to change that to "superceded" or something else. As a side note, I'll mention that I myself am retired, and I'll claim that that does not make me less dependable. But one

Re: [R-pkg-devel] [External] Re: What is a "retired"package?

2021-09-21 Thread Jeff Newmiller
I agree... but trouble is in the eyes of the beholder. If OP's approval process requires use of actively-maintained software, then use of code depending on one of these "retired"/"superceded" packages could indeed be a problem... for the OP. OP cannot expect to be able to impose those

Re: [R-pkg-devel] LaTeX issues on r-devel-windows-x86_64-gcc10-UCRT?

2021-09-21 Thread Struckmann, Stephan
Dear Thomas, thank you for your quick reply. I'll consider then writing to the CRAN address earler, if I have strong hints that the build/check system may cause a warning/error. So, I'll wait for the next check-run then. If I can help you in any way with fixing the pipelines, just ask...

Re: [R-pkg-devel] [External] Re: What is a "retired"package?

2021-09-21 Thread Hadley Wickham
> But for the broader question, Jeff is saying that there really are 700 > packages that are in potential trouble! I think that's rather an overstatement of the problem — there's nothing wrong with plyr; it's just no longer under active development. If anything, plyr is one of the safest

Re: [R-pkg-devel] [External] Re: What is a "retired"package?

2021-09-21 Thread Lenth, Russell V
OK. Well, as Noah has pointed out, I can just use apply to do what I need, and get plyr out of the picture. But for the broader question, Jeff is saying that there really are 700 packages that are in potential trouble! __

Re: [R-pkg-devel] [External] Re: What is a "retired"package?

2021-09-21 Thread Noah Greifer
apply() also recently got a 'simplify' argument, which means you request its output be returned as a list, too (i.e., to replace alply). Noah On Tue, Sep 21, 2021 at 12:10 PM Jeff Newmiller wrote: > As you previously quoted: > > > plyr is retired: this means only changes necessary to keep it

Re: [R-pkg-devel] [External] Re: What is a "retired"package?

2021-09-21 Thread Jeff Newmiller
As you previously quoted: > plyr is retired: this means only changes necessary to keep it on CRAN will be > made. That excludes bugfixes related to any specific use cases it is not currently capable of handling. In other words, if it doesn't handle the data you pass along to it from your

Re: [R-pkg-devel] LaTeX issues on r-devel-windows-x86_64-gcc10-UCRT?

2021-09-21 Thread Tomas Kalibera
Dear Stephan, On 9/21/21 3:31 PM, Stephan Struckmann wrote: > Dear all, > > lately, an error and two warnings occurred for our package dataquieR on the > platform r-devel-windows-x86_64-gcc10-UCRT > (https://cran.r-project.org/web/checks/check_results_dataquieR.html). > > Unfortunately, error

Re: [R-pkg-devel] [External] Re: What is a "retired"package?

2021-09-21 Thread Lenth, Russell V
... "I am not fixing this hot mess"??? To the contrary, the README contains a clearly expressed intention to maintain plyr to keep in on CRAN. RL -Original Message- From: Jeff Newmiller Sent: Tuesday, September 21, 2021 10:36 AM To: r-package-devel@r-project.org; Lenth, Russell V ;

Re: [R-pkg-devel] [External] Re: What is a "retired"package?

2021-09-21 Thread Lenth, Russell V
From: Andrew Simmons akwsi...@gmail.com > Doesn't apply already work on any dimensional arrays using argument MARGIN? Egads, yes it does! I can't explain why I didn't know that... Russ [[alternative HTML version deleted]]

Re: [R-pkg-devel] What is a "retired"package?

2021-09-21 Thread Jeff Newmiller
There is nothing official about that term. However, the meaning as intended by the package authors seems pretty clear to me, and if some organization decides not to allow software that is not being maintained to be relied upon then that is their decision. I don't think slapping a different

Re: [R-pkg-devel] What is a "retired"package?

2021-09-21 Thread Lionel Henry
Hello, We renamed "retired" to "superseded" some time ago to avoid any confusion. Superseded functions and packages continue to be maintained on CRAN for the foreseeable future and it is safe to depend on them. See the "superseded" definition in https://tidyverse.org/lifecycle/. plyr probably

[R-pkg-devel] What is a "retired"package?

2021-09-21 Thread Lenth, Russell V
I received a request that I remove the 'plyr' package from the Imports for my package, because plyr is retired. Indeed, the README file for plyr states: > plyr is retired: this means only changes necessary to keep it on CRAN will be made. > We recommend using dplyr (for data frames) or

[R-pkg-devel] LaTeX issues on r-devel-windows-x86_64-gcc10-UCRT?

2021-09-21 Thread Stephan Struckmann
Dear all, lately, an error and two warnings occurred for our package dataquieR on the platform r-devel-windows-x86_64-gcc10-UCRT (https://cran.r-project.org/web/checks/check_results_dataquieR.html). Unfortunately, error messages/warnings are likely related to the test system’s