-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add writeup of where to get package binaries #82
Comments
It sounds like a cool blog post topic indeed, I'll think about it, thank you! |
Just to clarify, are you volunteering to write it? Otherwise I can write it, not an expert either, but always glad to research such things. |
I ✋volunteer as (con)tribute 😄. Just wanted to make sure this would be a good platform for the topic and that I hadn't missed someone else's work on the subject. |
Awesome! I always think of that movie when writing "I volunteer" 🙈 Yes it's a good fit for the blog and I don't know of other write-ups either. You could write it when you have time, no hurry. We don't really have contributing guidelines but an example PR #50 and I can answer further questions. |
Just found this (recent) blog post by Colin which covers most everything: https://www.jumpingrivers.com/blog/faster-r-package-installation-rstudio/ |
ah, good, thanks! |
If you want to write your own perspective (linking existing stuff) and add some aspects, a blog post would of course still be welcome. |
as with #81 I'm always re-researching the whole package binary availability situation in all combinations of
Between the (public?) RSPM binaries (for some distros), Michael Rutters debian binaries, sometime-late (?) CRAN macOS binaries and renvs semi-related local global pkg cache, there seems to be a lot to consider.
I'm not the greatest expert on compiled packages, because I've never myself written packages with any compiled code, but I have struggled with this from the other end.
Is there a good resource for this already?
if not, might this blog be a place for a writeup about this?
The text was updated successfully, but these errors were encountered: