And every time you upgrade to the next major release, you start again from square one because the requirements of your software have changed. You get it to work and things seem to be fine. Over time, you start noticing things that are subtly broken, until something just fails completely and doesn't work. The fix turns out to be trivial when you give it another go two days later, but at the time it happened you really didn't have the nerve to deal with it right then.
After two dist upgrades, you realize that this approach isn't workable.
Well, I have two Debian desktop installations. One is six, the other one is ten years old. I never had a problem with either.
This is without adding the numerous servers which I just install and forget, and they work without any problems for years.
edit: Yes, they're dist-upgraded all the time.
Re:OpenBSD KDE Plasma Desktop
by PrimeMcFly on Monday January 08, 2024 @04:28PM
(#38918423)
> And every time you upgrade to the next major release, you start again from square one because the requirements of your software have changed.
Nah. That's a huge exaggeration. Most software doesn't change its base behavior like that and certainly not with every new release, and certainly browsers don't.
The workflow is you put a test system to “complain” mode and use your software as intended, and add the required permissions to the profile by looking at the logs to see what your app is doing. Then you put AppArmor to enforcing mode, add the profile to production system and your application is sandboxed. Iteratively refine as necessary.
Debian desktop comes with AppArmor enabled. Nothing has been broken so far.