Not to mention there are a ton of leftover config files, and legacy references that are no longer valid.
I’m glad I’m not the only one who loses Lima support upon upgrading to buster. I thought it was something inherently wrong with how I was doing it. Would simply doing a hold on the Mesa libraries be enough fo maintain support? I wouldn’t know which ones would need to be held.
I remember back when I used cfw on my mobile phones, I would have an “aroma” installed, allowing me to install whatever component I want upon flashing my image, essentially building it on my first boot.
I would love to see a completely clean slate environment that could be built up like this; packages all existing on the image, ready to be built.
In fact, this is similar in concept to the NOOBS image provided by the raspberry pi team.
Here’s what @guu did, along with a lot more discussions surrounding it: Custom D.E.O.T. V1.0+/Clockwork OS v0.4 image - With Updated Kernel 5.3.6, Latest Lima Drivers, RA1.8.1, Mupen64+ and much more! (Current version: 191122) - #71 by guu