Is it just me, or is packaging for Flatpak a nightmare?
I'm trying to package and publish a tool I've been working on, but for the life of me, I'm struggling with Flatpak.
It's a wails app, that relies on webkit2-4.0 and some additional libraries that are not present in any of the Sdks I'm using. (javascriptcore, etc...)
To get those libs, I tried building the app AND webkit itself against the specific platform. But since webkit takes such a long time to build, I'm running in circles.
I've been trying for a while, looking up other manifests helped me but I'm still lost on a few things. Maybe we could help each other. I am the creator of open-tv.
I managed to get it somehow working, but it got rejected by Flathub, because they don't want me to build webkit and use the network during build (which I need)
Not relying on the network during a build is pretty common while making an rpm package. It's a pretty reasonable requirement to have. I'd suggest looking into what e.g. the equivalent Fedora package does.
Noice! I got a successfull build of a flatpak bundle (without webkit) using GitHub actions. the bundle can be downloaded and installed via flatpak install --user xxx.flatpak and it's running.
Now I need to figure out, how to publish this to Flathub.
I had assumed, since I can do flatpak install org.gnome.Sdk and select 3.38 (there are even older 3.x versions to select from), that they left it for older GTK apps that are not (yet) compatible with newer runtimes.