Is it just me, or is packaging for Flatpak a nightmare?
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.
Welp.
You're viewing a single thread.
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)
I'm working on resticity, a restic frontend.
Is that webkit version outdated? In general you should try to support one of the supported versions.
TBH I'm fairly new to this. Gnome 45 sandbox has webkit2-4.1, while my PC build uses webkit2-4.0. Now, Gnome 3.38 sandbox has webkit2-4.0, but it still doesn't run, due to missing libs. And I don't know how to put everything together, so it works without having to re-build everything.
Hm, I would contact upstream devs to support 2-4.1 then and find / create git repos for the missing libs, then include those as binaries in your manifest. This should avoid network access?
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.