Flatpak packaging

[tinywrkb]

I quickly packaged here ddcui as a Flatpak to have the app decoupled from the base OS and built with the KDE Flatpak runtime.
Users who are running immutable OSs (Silverblue/Kinote or Endless OS) might appericiate having a Flatpak packaging manifest for building and installing the app.

I don't think that this is suited for distribution via Flathub, as it expect that the host system would be set to allow access to these i2c devices.

Note that the packaging manifest includes x-checker-data properties for easily automating module version updates with flatpak-external-data-checker.

It's not something I recommend doing, but it's possible to use this packaging manifest to generate a Flatpak bundle, and then distribute the packaged app as a single file installer, though in that case I suggest adding separate-locales: false to the Flatpak manifest.

[rockowitz]

Thanks for the post. Packaging ddcutil/ddcui as flatpack/snap/docker images is on the future enhancement list, but the devil with doing so is all the details that are apparent only to someone familiar with the framework and integrating it with the existing workflow. If you can provide a pull request I'll consider adding it to the existing ddcui package or creating a new package, as appropriate.