Because I'm a glutton for punishment, I'm resurrecting (trying for a third time) {getCRUCLdata}. I'm not even sure that anyone uses it, but since I still have it sitting around, I've overhauled it and rewritten it to remove any caching, using {rappdirs} got me in trouble the first time, using R's own user cache directory got me in trouble the second time. So twice archived, now going back with no caching aside from in-session via {httr2}. https://codeberg.org/ropensci/getCRUCLdata #RStats #ClimateData
getCRUCLdata

CRU CL v. 2.0 Climatology Client for R

Codeberg.org

@adamhsparks Good luck! You seem prepared after exploring all options.

How did the custom R cache directory led to problems? It was about not removing/cleaning it?

@Lluis_Revilla I don’t recall. I was so frustrated after using two solutions that were supposed to be “CRAN safe” that I just gave up for a year or more between my efforts.

@adamhsparks I have mixed experiences with rappdirs. It doesn't store in the CRAN-approved paths but some packages used before that policy change.

About R own path, I recall some discussions/complains about cleaning up.

In any case I hope you get it working on CRAN now.

@Lluis_Revilla it was on CRAN for a few years before being unceremoniously archived due to {rappdirs}. Nothing flagged when I submitted or updated. Just out of the blue they didn’t like it. So I tried their own cache directory and didn’t write anything there. Just set up infrastructure. Archived again.
@adamhsparks I see, thanks
@Lluis_Revilla you’re probably already aware, but see this from @steffilazerte back in 2021. https://github.com/r-lib/rappdirs/issues/40
Using unallowed path? · Issue #40 · r-lib/rappdirs

Happy New Year! In my weathercan package I included an option for saving a data frame of stations data to a cache directory, found with rappdirs. stations_file <- function() { file.path(rappdirs::u...

GitHub