![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/h1ChnLuBHr.png)
I guess so, it doesn’t hurt if you don’t mind the inconvenience
I guess so, it doesn’t hurt if you don’t mind the inconvenience
DivestOS on my tablet
Cool, there are supported tablets now?
Oh I thought that was only Artix, what does CachyOS use?
Non c’è scelta, se l’ultimo italiano dovesse lasciarci, allora anche questa informazione dovrà lasciare l’umanità
Rememeber, whenever you break one spaghetto you break one heart 💔
If the client (which encrypts the data in for an E2EE service) is open source and has also been audited by third parties than there’s little reason to do so
You may not understand, but we do.
Questo segreto rimarrà custodito gelosamente dalla stirpe italica. ◉‿◉
Is that so? From the issue I read there was no way around it because the two images are fundamentally incompatible once you layer that package, you had to remove the layered package, it seemed from the discussion that they might have “fixed” the base image at some point as a pull request was opened on Pagure. I waited a bit for it to go upstream, but nothing happened for a long time and just went thorugh with the manual intervention, and actually, now that I check it again, the maintainer siosm commented that they can’t accept the PR
Doesn’t Bazzite have the base image modified to have the codecs included already? I think that’s probably why you didn’t experience any disruption there
- Full hardware accelerated codec support for H264 decoding.
link: https://github.com/ublue-os/bazzite/?tab=readme-ov-file#about--features
Love the irony, but this is painting a little too good a picture
Every update is just… meh. Smooth, new, fresh system not affected by my stupid tweaking and breaking
Most times yes, but major updates usually cause some trouble, like from 39 to 40, you couldn’t do it without uninstalling the codecs for Firefox. Firefox that is installed by default as an RPM, because the Flatpak Firefox doesn’t yet have 100% compatibility with all the features that work with the RPM, so as a user you’re pretty much led to get yourself stuck in this hole, not too difficult to fix in the end, but still a pain to find out and fix.
Everything else is 100% true! And I think it will be always hard to beat as an implementation of immutability (second place only to NixOS imo), A/B partitioning doesn’t hold a candle to OSTree
TL;DR Don’t (unless your needs are really basic or you really don’t want to layer more packages)
Distrobox ftw, its website is pretty good to find all its features and it has a neat GUI BoxBuddy too! And also the generic Pods can be useful for more advanced needs.
Extra tip: if you have more time to spend on learning, I think Nix Home Manager will actually be the better solution in the long run, no need to worry about containers breaking in some way after system updates with scattered solutions that are hard to understand and remember, also you get to bring your configuration anywhere
You use the AUR because you want more packages.
I use the AUR because I believe in humanity.
We are NOT the same.
Ahh, thank you
Outfits? What does it mean in this context?
Both features are important IMO, reproducibility is for being able to define certain aspects of your machine in a way that you can nuke it and, as long as you have its configuration (declarative for Nix, other implementations might have it as imperative), bring it back just how it was set up, without differences or breakages; while immutability is for being always confident that whatever* you do to your machine, you won’t be able to break it because the root, which holds the functioning core of your system, can’t be messed around with, NixOS has both I believe.
*not really “whatever”, because there are still some ways to break, but you have to be very deliberate in doing it (think rm -rf /*
), but in normal operation you won’t just somehow install something or upgrade your packages and be left with an unusable system
I think ublue is the best incarnation of this style of “tweak forks”, it meaningfully expands on the base, but still remains compatible with the original since you can just do a rebase from one of the original Fedora Atomic spins… which wouldn’t have been possible without OSTree, so thanks, Fedora devs :)
How about you let me save the application data for myself and keep it secure on my equipment first, Google? Uff, going through the salvaging process of the data on my near-broken phone is being the most excruciating thing I’ve done recently because they just won’t let you access and save it unless you rely on their cloud… which I might eventually just do, just wished it’d at least be a 100% safe way to get everything, but no, they had to put the decision to be backed up into the applications’ hands ;-;
I lowkey want this, it’s like the system equivalent of the screen cat (btw does that exist but with Wayland support?)
L arge
L regex
M odel
That’s class