I’m afraid you don’t really understand the problem. A large development effort with a broad set of dependencies is developed against target versions. Once the software is released (and in reality, long before), these versions are no longer “new”, but must be updated in lockstep with the custom code or else methods and classes and libraries can change drastically, leading to exceptions and segmentation faults and memory leaks and kernel panics and guru meditation. You may have noticed with RuneAudio that you can’t really modify the image at all without it breaking, and that is precisely because the second you modify it you force yourself into updating the package tree and replacing a lot of core dependencies right out from under RA. Arch is a wonderful end-user system [which is good because that is the design goal], but it is truly a horrible target for an embedded appliance [fine, because the design goals that benefit embedded/server market wreak havoc on usability (CentOS….)

I have the same experience. Using Digi+. Finally I run runeaudio..

Thank you Daniel!! Enjoy!