On 24.03.19 21:00, Neal Fultz wrote:
> 3) Adopt package, push fixed one to CRAN - not sure what the exact process
> is for un-orphaning, or if I would want to commit to maintaining it without
> knowing more about why it was dropped and how much work it is to get it
> passing. Eg if it were patholog
When I attempt to install it the error indicates that the maxent package
is not available. Attempts to install that package fail with more errors
than can fit on an Rstudio console, so I cannot even scroll to see the
first error.
You could simply remove the dependency on that package if your
Neal,
"It's complicated". To a first appromimation, a dependency is a risk.
As an illustration, I taught CRANberries a few years in its run to also
consider disappearing packages. Right now, it knows about 3685 packages
which are (or were at some point) "archived". This is an imprecise count
One of my clients has a shiny app which depends on RTextTools, which was
dropped from CRAN for lack of maintenance.
What would you all recommend in this situation? Here's a couple options I
could think of:
1) Vendor the orphaned package - we are doing this for now. I'm not a fan
of this, because
