Differences between Debian Testing and Solus

SisuAika

I'm an enthusiastic user of both Debian and Solus. Recently, I installed Debian Testing (Trixie) for my gaming rig and updated the kernel (Liquorix 9.13.x) and Budgie (latest version) and have an enjoyable system running. This is my first time trying Budgie on Debian, though I usually always install the Budgie version of Solus.

At any rate, this got me thinking about how similar these two experiences were becoming for me and I was hoping someone with a bit more Linux knowledge could explain the appreciable differences of running a point release testing branch (as opposed to a true rolling release) and what other interesting differences there are between these two projects on a technical/design level?

Just looking for thoughts, since my own knowledge was lacking.

nolan

From the Solus side I can say that the "curated rolling release" is an excellent option, it's set between a pure rolling release and a point release, usually the solus team release updates every Friday/Saturday and critical updates like hot-fixes and security updates are released the same day as they land (cherry-picket), for example: hypothetically, Firefox got updated the weekend as usual and a security update was released Sunday, that security update will land in the repo the same day or the next and the user just need to update as always. An other hypothetically case, lets say inkscape released a new update Sunday or the same day as solus release a weekly update, that new inkscape version will be available the next weekly update. For mayor updates like a new mayor version of KDE or GNOME 49 for example, the updates will be paused (no weekly updates for one week normally) so the team has time to test with testers and to be sure no bugs or instabilities are left that can affect the end user and the updates will be resumed wen they think everything is ready (this in the time frame of one to two weeks, unless something out of their control happens, luckily hasn't happened yet).

SisuAika

nolan Thank you for pointing our the curated testing bit! I can attest to this as Debian Testing just pushed the latest GNOME and I wasn't ready for it on my other machine and it broke all my extensions and caused a few other headaches for me. It was a little more of a raw experience.

nolan

I read that debian testing receives packages from debian unstable and the only requirement to send from unstable to testing is that the package must be in testing at least 2 to 10 days. Anyways testing should no be considered as a daily driver as it still in development and not aimed for the end user IMO.

AlphaElwedritsch

In my opinion, the only thing they have in common is that they are both Linux distributions. Otherwise, they are miles apart. System structure, package management, etc...

SisuAika

AlphaElwedritsch This is what I'm interested in. I'm familiar with eopkg, but can you expand on the System Structure?