We just released a blog post about something I'm very excited about: Great Docs. Post is in the *new* Posit Open Source site:
opensource.posit.co/blog/2026-04...
Great Docs is a #python pkg for creating beautiful Python package websites. We make it easy to use but also give you lots of options.
Some R client tools (e.g. renv, pak) also automatically set the PPM linux binary URL for you for smoother cross-distro use.
And... look out for R 4.6 which is coming with native linux binary support built into R, so eventually all this special config will go away, and you just install.packages()
The options() code there is arch-agnostic, using R.version["arch"] to detect arch when you start R.
But if you want cross-distro agnostic, you can choose "manylinux glibc 2.28+" as your distro and get wheel-like portable binaries based on RHEL 8. System libs there will be older though.
Why not both, archive the private repo with history intact and publish a copy of the repo with a clean slate :)
That's what we'll do when there's potentially sensitive info in the repo, e.g. at one point someone accidentally committed credentials
Oo yeah I remember libgit2 in EPEL 9 now. There was some CVE back then I think, that did get backported, but they ended up breaking it anyway
GDAL 1.x on RHEL 7 is rolling in its grave right now 😂
Thanks for the heads up, rebuilding all older geospatial packages now. I've never seen RHEL let major ABI breakages for a big library in like this, esp years after RHEL 9's release, but I guess that can just happen now 🤷
Announcing the Winners of the 2025 Posit Table Contest! 🏆
The data community showcased stunning work in #RStats/ #Python using gt, Reactable, and #Quarto, transforming complex data into beautiful, effective communication.
Congrats to all the winners!
See the innovation: posit.co/blog/2025-ta...
P3M should be updated now. There was a bad symlink on CRAN that affected us and others mirroring CRAN, and CRAN fixed that this morning.
Going forward, we'll try to communicate these issues better using status.posit.co
For reporting P3M issues, no direct email but posting on forum.posit.co works
Even with LLMs, I'm not sure this approach is for everyone. but if you're like me years ago, trying to jam custom JS into R and finding it horrible to develop/maintain, I think it's worth going full web dev and getting all the benefits of proper tooling + unlimited JS libraries on npm
I've been trying this out recently and it works great! simplifies the JavaScript <-> R communication a lot. I've updated my Shiny+React example app to use this, as another example: github.com/glin/shiny-r...
#rstats
yessssss, arm64 linux binaries in posit package manager!! #rstats packagemanager.posit.co/client/#/wha...
A screenshot showing the Logfire tracing UI with traces from a Shiny app using ellmer, httr2, and mirai on the left and some attributes on the right.
A Shiny chatbot with a conversation about the weather in Atlanta, GA. It clearly serves as the source of the traces in the first image.
More #rstats + OpenTelemetry news: @schloerke.com finally got all of the async issues in {ellmer} and {shiny} sorted out and tracing now works!
Here's what combining {shiny} + {ellmer} + {httr2} + {mirai} + {otel} looks like today.
(All credit for the screenshots to @schloerke.com.)
reactable now has an AI chatbot for docs, thanks to kapa.ai's open source program: glin.github.io/reactable
It's been neat to see it in dplyr, arrow, the Posit docs. also wicked cool that it can index GitHub issues too and dig up answers to old questions that I've long forgotten :D
#rstats
Besides the repo URL change, we're also working on eliminating the `apt install deps` step with more wheel-like binaries that bundle their system dependencies. posit.co/blog/introdu...
Probably still makes more sense to use conda pkgs w/ conda R, but these sidestep some compatibility issues at least
Posit products and community tools have mostly baked in the config step, so it's only these very uncommon cases, e.g. conda R run from the terminal, that hit this issue. That's why we hadn't realized this was a bad documentation issue a lot earlier, so sorry about that.
There's a long story of why it's like this. To summarize, I guess:
R has never natively supported linux binary packages and this PPM "support" is bolted on.
Binary installation used to just work in the past. A recent-ish R bug that was never fixed made this config step necessary.
Correct! Adding to what Lachlan said, pretty soon you'll be able to use a repo URL like p3m.dev/cran/latest/... and it will *just work*. The current docs are indeed leaving out that critical step, but we're removing it completely because of how awful it is to configure yourself.
