Hi there,

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

There is CI running it on every push to dev, on trixie which has been passing 
nicely for a while now.

To be clear about intent: this is a demonstration that 5.0 can be packaged 
without a patch stack, which hopefully can be  picked up and done properly. I 
am definitely not trying to take over the archive package! 

Some things I already know are not right, and would value your view on:

* 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.

5.0 is at RC7 with a final release imminent. 

I’m very happy to make any changes and happy to answer questions should you 
have any. 

Thanks again,

Sam

Reply via email to