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.

  • corsicanguppy@lemmy.ca
    1·
    8 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
        11·
        8 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!

  • Fredol@lemmy.world
    0·
    8 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
      0·
      8 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.

      • baru@lemmy.world
        1·
        8 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
    0·
    8 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.