Hongli Lai
It is not. Setting `RBENV_ROOT` to a single directory would mean every user has to have write access to that directory in order to install Rubies. Setting `RBENV_ROOT` also means...
No objections to that approach in principle, but there is one complication: all plugins, including ruby-build/rbenv-install, will have to be updated to support this new `RBENV_ROOT` format. Are you okay...
@mislav What's your opinion on the above?
Let me explain my use case a bit better. I am looking to distribute Ruby binaries in the form of Debian/RPM packages. The problem with the current distributions' Ruby packages...
Hi @mislav, have you been able to come to a conclusion?
Hi @mislav, it's been a while, can I bother you to have a look at this again?
Thanks mislav. No core requirements changed, but I did receive a bunch of feature requests that may be worth taking into consideration. - A secondary path (besides `RBENV_SYSTEM_VERSIONS_DIR`) to look...
In Passenger we use writev() to perform a gathered write. This way we don't even have to allocate that final string. Not sure whether Ruby core has support for writev...
Actually we still need it in order to make [speeding up the CI](https://github.com/fullstaq-ruby/server-edition/blob/main/dev-handbook/speeding-up-ci-feedback.md) work.
All images have been moved to Github Container Registry. But we don't auto-publish yet.