flatpaks VS pkgbuilds

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.

Getting environment variables from systemd generators, so they only needed to be set for the systemd user session (environment.d, custom generators), and they cover this way also systemd user services, systemd-run and flatpak-spawn. Also, bash-complete-alias is pretty neat, though I'm making limited use of it these days, and prefer wrappers, and symlinks.

And here's a more advanced one.

You can use 30-systemd-environment-d-generator to read and then export them, here's an example.

If you're using ranger then you might also want to set TERMCMD. I don't remember what it's used for, maybe for launching new terminal windows from ranger. There are HW video acceleration vars, I set them dynamically with a systemd environment generator.

ttf-liberation as the bare minimum, with a gschema override and proper provides array in a PKGBUILD to avoid both adobe-source-code-pro-fonts and cantarell-fonts.

The whole mess is in my pkgbuilds repo, so feel free to look around and ask.

Ignore everything that starts with my/uosys-mods-. Also, everything that starts with my/ is personal packages, you can replace them with the original upstream packages. For reference: flatpaks, pkgbuilds.