Post #2352280
2025-02-06 03:29 UTC
Replies (4)
-
@HydrePrever@mathstodon.xyz 2025-02-06 04:30
@jimbob@aus.social the fact that the "don't run" examples are tested never ceases to amaze me. I have had to comment some examples to avoid this. How convenient for the user... Also, checking _R_CHECK_LIMIT_CORES_ on package load to totally disable multi threading was at some point the only way I found to stay on cran EDIT m'y bad, it's the "don't test" examples that are tested... The"don't run" seems safe
-
@barbone@fosstodon.org 2025-02-06 05:04
@jimbob@aus.social While the SSL certificate is unfortunate, the part that failed was not wrapped with `\dontrun{} -- it was the download.file() after it. Oddly there's a second \dontrun{} afterwards. https://cran-archive.r-project.org/web/checks/2023/2023-02-27_check_results_insol.html https://github.com/cran/insol/blob/4fe6f26351af22121a5319b4a8b4950b66ca6226/man/hillshading.Rd#L60-L61
-
@jospueyo@fosstodon.org 2025-02-06 05:59
@jimbob@aus.social 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
-
@gavin@fosstodon.org 2025-02-06 08:26
@jimbob@aus.social I don't have time to test the use of nix for this, but if it is archived in nix, you could run the {insol} code in a nix-shell, and get around the CRAN issue.