flatpaks VS sway

See example here, this, and also.

p.s. This is how a real full FFmpeg build looks like. Note the extra dependencies.

This needs to be on Flathub. I created an initial Flatpak manifest here. You should consider renaming the app id to org.rncbc.qpwgraph, as you already own the domain.

You most likely can do this via Podman/toolbox. I haven't tried this with Silverblue, my daily driver is Arch Linux, but it's also immutable, so I put the whole libvirt stack in a Docker/Podman image, and I also have virt-manager packaged as a Flatpak. It's very much a WIP, and only rootful, non-privileged, host network namespace is tested and confirmed working. Also be aware that at least with the Fedora image, rootful and privileged broke my host, as I probably need to mask some systemd services/targets in the container.

Why not? I'm personally using a couple of TUI apps myself that I packaged. There are a few limitations in Flatpak affecting TUI apps, but if it's a single executable app, then Flatpak package can work great for it.

Example app: Notepad++

There's no Fuse support in the Flatpak, this needs the setuid bit set and run as root, so the AppImage cannot run in the sandbox. We can extract the AppImage and repackage it as a Flatpak, and I believe that there are more than a couple of Flathub apps that does this. Here's an example.

Adding to @Popular-Egg-3746's comment, it should be noted that libimobiledevice's libs & tools can definitely work when packaged in Flatpak, you just need usbmuxd daemon running on the host, and distros like Fedora Silverblue/Kinoite are shipping it pre-installed. I actually packaged ifuse as a Flatpak, and used it a little, see.

For anything other than games, you need the Collabora fork. I'm building this as Flatpak app, see here. DXVK is not included, as Vulkan wasn't supported in the Wayland branch when I initially packaged Wine. I believe that now Vulkan should work.

I have them packaged here.

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).