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
This is a good point. I would prefer to include all the data in the
package, but CRAN has strict limitations on package and subdirectory
size, which the potential data would easily exceed. Whether it is an
active binding or a get function, dynamically downloaded data will
always suffer this pro
--- Begin Message ---
Don't want to turn this into a pile-on, but I also think this isn't a very good
idea. As I understand it, accessing the symbol "foo" will pull the latest
version of foo from the remote site. This has consequences for reproducibility,
because now your code could be exactly t
