deleted by creator

Since you didn’t post your solution, here it is for others: you need to add Flathub as a user remote too.

flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

It’s not called systemD. It’s just systemd.

deleted by creator

deleted by creator

deleted by creator

In this case, it’s an enthusiastic employee working for his own benefit, being able to play the game on his preferred OS. And thankfully recognized and supported by the company.

I think Discord and Spotify are similar situations. The companies don’t particular care, but a few employees wanted it and made it happen.

I uninstalled the game from within Steam. At that point it should know that the game was no longer installed because (1) I told Steam to uninstall it and (2) the Baldurs Gate 3 folder was gone.

Ahh why does Steam have to be so garbage. I wanted to try it out so I renamed the Windows version (so I could benchmark it later without redownloading it), uninstalled it. Then when I reinstall it, Steam doesn’t even download anything, it just assumes it’s still installed for some reason, so it gives an error trying to launch it since there’s no game files.

iOS 26 does have some nice UX improvements (I like that popups happen right by the buttons that activated them and the new camera app), but it’s undeniable that Liquid Glass has made legibility worse and more inconsistent.

And I don’t think it’s valid to say “oh it’s a new release, they’ll iron things out later”. We should expect quality releases from one of the richest companies on Earth with some of the best engineers. Apple did not have to release Liquid Glass in its current state.

Yes. GUI stores tend to use something called PackageKit. It’s basically an abstraction layer, each package manager writes its own packagekit backend.

That way, GUI stores just have to support PackageKit rather than every single package manager. But there are bugs with PackageKit and the backends may have bugs too. Pacman’s is notoriously bad.

That’s not what this is about. It seems like several Red Hat teams have been merged into IBM.

deleted by creator

deleted by creator

This comment should be deleted soon

This comment should be deleted soon

This comment should be deleted soon

For me, the issue is that it’s too dense. Act I and II are much more spread out. By comparison, Act III is overwhelming and there’s so many people to talk to.

I wish it was made a bit more linear, because the content itself isn’t bad, just the delivery IMO.

The ffmpeg from Flathub is a “runtime” package, intended to be used by other flatpak apps. It’s not meant for CLI use.

Flatpak apps are not added to your $PATH. They’re run with flatpak run appID. Though again, ffmpeg is not an app so it cannot be run this way. Though technically you could use it for CLI use by doing something like flatpak run --command=sh org.mozilla.firefox. This will open a shell inside the flatpak environment, which can use the ffmpeg flatpak runtime.

Though now that I think about it, it would be fun to create my own flatpak package for ffmpeg for CLI use. Should be pretty simple, it would just be a mostly empty package that relies on the ffmpeg-full flatpak runtime.

You’re just adding arguments on arguments that aren’t making any sense now. You’re original comment and understanding has been addressed.

My main point is that I’m worried about additional complexity. On most atomic distros, you’re not supposed to touch the base system, so various tools are preinstalled or available: flatpak, podman, homebrew, snap, appimages, systemd sysext.

The BSDs seem to enjoy a separation of OS and user packages with reduced complexity. Though their task is easier since they are complete operating systems, whereas linux is just a kernel and many different projects put together, and many different groups putting out their own distros with varying packages and compatibility.

Both RPM and dpkg support being able to unpackaged or install packages into your local home directory

These don’t seem to be advertised features. More like hacky workarounds. Complex rpm commands. Ubuntu thread with various proposed solutions.

It would be really cool if dnf and apt got good, easy, simple support for installing packages into the home folder. But that’s not what’s happening. The proposed solution seems to be systemd sysext, which again, prompted me to have worries about complexities about how software is being managed on more “modern” distributions.

You’re just adding arguments on arguments that aren’t making any sense now. You’re original comment and understanding has been addressed

And I keep discussing it because I enjoy doing so.