On Wed, Aug 05, 2026 at 12:22:11AM +0100, Sam Aaron wrote: > Sam Aaron here - I maintain Sonic Pi. (Note I'm not subscribed to the list, > so please keep me in CC on any replies.) > > Firstly, thanks Valentin for all your work getting 4.6.0 into unstable and > testing. I just wanted to give you a heads up about the upcoming v5.0 as the > dependency situation is very different. > > The short version: Erlang and Elixir are gone, and so is SuperCollider. > > The audio engine is now SuperSonic, which is built from source in tree, so > supercollider and sc3-plugins are no longer dependencies. Instead it’s Rust > (cargo and rustc, for the MIDI and gamepad subsystems), > > I have recently worked to make 5.0 package cleanly, with the specific goal of > you not needing many (if any) additional patches. As a demonstration there is > now a packaging/debian directory in the upstream tree on the dev branch: > https://github.com/sonic-pi-net/sonic-pi/tree/dev/packaging/debian
Hi Sam, Thanks for the update, this is great news. I saw that v5 was happening in github but did not know about the timeline. For Debian the main problem is usually dependencies that need to be included in Debian repository, so we cannot pull packages from cargo. I will try to check this and let you know how it goes. > * The Policy build uses stock QScintilla, which means it misses some > accessibility fixes we carry in our vendored copy. What’s your preferred > direction with this? > * We drop the native Ruby extensions in the Policy build and fall back to > pure Ruby. > * The Debian changelog entry in tree is a placeholder and clearly yours to > own, not mine. Thanks, minimal diff with upstream is always prefered in Debian, so we can discuss what we can do about these changes. -- Valentin
