Looking into some #rstats code attached to a paper.

The code won't run now, because it relies on a package that has been archived (removed) from CRAN.

This package had been around for over a decade, with updates over a time.

Looking into why it was removed, it appears that one of the package examples required downloading a GeoTIFF file from a website. It seems that, at the time CRAN tried to run and test this code, the server hosting that file happened to have an expired SSL certificate. The certificate and website is now fine. The example code was marked "don't run".

Maintainers, understandably, gave up on CRAN's bullshit and have not bothered with the package since, or trying to get it back on CRAN.

Good job, CRAN.

meteoexploration.com/R/insol/

@jimbob CRAN has a lot to improve, I agree with this. However, the fact that CRAN is so restrictive is one of the reasons why installing dependencies in R is usually an easy and smooth process. Comparing, for example, to the Python nightmare.

#Rstats

Follow

@jospueyo @jimbob I've used both, and both as a maintainer and a user I prefer python by far. The absence of a proper version / dependency solver in R, forcing one to rely on CRAN snapshots for reliable setups, borders on unusable for developing any kind of somewhat complex system. As a (co-) maintainer of a CRAN package, the very existence / need for something like revdepcheck is somewhere between concerning and insane.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.