Interesting, I’ve never heard it described that way. I’m running Bluefin for a year, and up to now I’ve just avoided making any system level changes. I run flatpacks for most things, and containers for any odd bits that need dependencies.
Is what you’re describing, using rpmostree? I haven’t used it yet, afraid of messing things up, because I LOVE the stability I have now.
Used to run Ubuntu, and I’d reinstall for every new release, because I’d already mucked up my install anyway so might as well start fresh. And other times I’d just break stuff so thoroughly I needed to reinstall.
Yes, you’d use rpm-ostree install on some downloaded RPM after adding the repo manually in /etc for updates later (they really make it painful because layering system packages should always be a last resort).
You’re doing things correctly already. If everything is working fine with all the applications installed in a containerized way (distrobox, flatpak, etc.) no need to mess with rpm-ostree.
100% I was in the same boat as you with the yearly Ubuntu refreshes, and that got so old. Now if there’s an update the breaks something I just rollback and pin the working version until there’s an update that works or I have time to troubleshoot the issue.
Interesting, I’ve never heard it described that way. I’m running Bluefin for a year, and up to now I’ve just avoided making any system level changes. I run flatpacks for most things, and containers for any odd bits that need dependencies.
Is what you’re describing, using rpmostree? I haven’t used it yet, afraid of messing things up, because I LOVE the stability I have now.
Used to run Ubuntu, and I’d reinstall for every new release, because I’d already mucked up my install anyway so might as well start fresh. And other times I’d just break stuff so thoroughly I needed to reinstall.
Yes, you’d use rpm-ostree install on some downloaded RPM after adding the repo manually in /etc for updates later (they really make it painful because layering system packages should always be a last resort).
You’re doing things correctly already. If everything is working fine with all the applications installed in a containerized way (distrobox, flatpak, etc.) no need to mess with rpm-ostree.
100% I was in the same boat as you with the yearly Ubuntu refreshes, and that got so old. Now if there’s an update the breaks something I just rollback and pin the working version until there’s an update that works or I have time to troubleshoot the issue.