Hey folks and welcome to another update of real-time editing of issue descriptions this week, I am going to give a short update on the progress of shipping by Ruby to gitlab um by Ruby is the gem that I've been working on for quite a while. It has multi-platform, builds it's ready to ship, but adding to gitlab is going to be another challenge.

um We have two primary issues. One is we require a somewhat up-to-date Butler version and we need to also be able to probably build a native extension in gitlab, even if we have multi-platform binaries provided by rubychamps.org. The reason for that is that we have the GDK that needs to that needs to work.

On a you know, a variety of um of of devices and setups, so people need to be able to contribute after the gem has been added, and the second reason is that we also have a fairly complex CI pipeline for gitlab itself and it's not trivial to make sure that the that the Champs are installed, that the chamber is always installed from a pre-built binary, but sometimes it just wants to.

It just needs to build the binary itself, so this leaves me with a decision either um not using by Ruby at all or going the hard route of figuring or adding rust support to our compiler tool chain or set of set of compiler tool chains. It's probably going to be the letter because otherwise it would give up on the idea of using the ruby gem and um yeah. This is going to consume a ton of time because it's necessary okay, that's it see you soon.