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.

  • Fredol@lemmy.world
    29·
    3 months ago

    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.

    • adONis@lemmy.worldOP
      152·
      3 months ago

      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.

      • Pantherina@feddit.de
        11·
        3 months ago

        Is that webkit version outdated? In general you should try to support one of the supported versions.

        • adONis@lemmy.worldOP
          3·
          3 months ago

          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.

          • Pantherina@feddit.de
            5·
            3 months ago

            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?

      • baru@lemmy.world
        11·
        3 months ago

        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.

  • taladar@sh.itjust.works
    20·
    3 months ago

    Well, I would agree in general but also anything involving khtml/webkit/blink and its various other forks is a nightmare to compile.

        • Russianranger@lemmy.world
          11·
          3 months ago

          Yeah I think you need a dock though, or if you don’t have the money to buy a dock, I think you can rent one of those POD containers. Still trying to figure out how to connect to this guy’s computer though, they locked it and I don’t know where to DL the libs for it

  • LiveLMEnglish
    13·
    3 months ago

    I’m currently helping package some dotnet apps and so far yeah it kinda sucks

    Though at least on my case dotnet might be more to blame

  • corsicanguppy@lemmy.ca
    115·
    3 months ago

    So us security/enterprise types hate it AND packagers hate it?

    We’ll have all of you back building 12 different package formats in no time!

      • adONis@lemmy.worldOP
        43·
        3 months ago

        yes… since it’s way easier to distribute, anything, by anyone.

        Speaking of which… I’m the official maintainer of all the crypto wallets out there… trust me, bro!

  • adONis@lemmy.worldOP
    6·
    3 months ago

    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.

  • adONis@lemmy.worldOP
    41·
    3 months ago

    Bummer! Flathub doesn’t want me to use Gnome 3.38, since it’s EOL :-(

      • adONis@lemmy.worldOP
        3·
        3 months ago

        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.