

Pixels have better security features than Samsung and doesn’t prevent you from using third party OSes.
More details here: https://grapheneos.org/faq#recommended-devices


Pixels have better security features than Samsung and doesn’t prevent you from using third party OSes.
More details here: https://grapheneos.org/faq#recommended-devices
I’m saying that we should be able to use package managers like DNF similarly to homebrew. Rather than managing system packages, it would only be used for packages the user installs. Whether it installs them into /usr/local, /home/dnf, ~/.local/bin doesn’t matter. All that matters is that it’s not managing system packages or mixing system-installed/user-installed packages.
Homebrew isn’t perfect. Awhile ago I tried to go all homebrew for my packages, but sshfs ended up not working (maybe a SELinux issue?). So I had to fallback to overlaying the package. Simiarly, I tried to install tailscale from brew, couldn’t get it to work.
It’s just that in “immutable” (I know how much you hate the term lol), there’s package manager fatigue.
sshfs and tailscale didn’t work for me there.My thesis is essentially that we’re creating too many package package managers with too many compromises. Traditional package management is far from perfect, but at least those package managers, you can do essentially anything. Brew could be that, if it had more GUI apps and maybe better SELinux integration (I say that not knowing for 100% sure that SELinux was the cause of my sshfs issuse). I would like for people to take a step back and find simpler solutions, make a single package manager that can handle any kind of package.
Edit: correction, tested again and sshfs is actually working, not sure what was causing the original issue. though I still have sshfs overlayed, maybe that provides some necessary dependency or SELinux tweak?
Edit 2: after removing the sshfs overlay, the sshfs brew package also stops working, so it seems like some host configuration is needed for the brew version to work.
So if i were to “sudo dnf install neovim” on Bluefin, that would install Neovim to ~/.local/bin?
I didn’t mean to say that Universal Blue specifically was making new package managers, but that in general new package managers have been created specifically to solve problems introduced by going immutable/atomic/image-based/whatever.
It’s not how you “generally” do it because many immutable distro developers keep developing additional ways to do package management that are more and more complicated.
I still don’t get why we can’t have a BSD like approach. Make usr, bin, sbin read-only. But have /usr/local be writable and have a traditional package manager install to that location instead.
Arch is quite an old distro and extremely popular. Valve could have chosen any distro, but settled on Arch.