• Samueru
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    2 months ago

    That is .firefox etc.

    There is actually a workaround for firefox, but for flatpak you would essentially have to make flatpak have its own home dir, and that is just too much of a hack for such application. As every app being called in flatpak would be under this fakehome as well.

    I guess you cannot update an app anymore when doing that.

    I could make a script for am that does it btw. I’ve never had the need to do this but it is possible.

    The script would run ./*.AppImage --appimage-extract the newly installed appimage, rm ./*.AppImage && ln -s ./squashfs-root/AppRun nameof.AppImage and that is it, it will work with the old desktop entry and symlink in PATH and every time the appimage gets updated it does the same thing like a pacmanhook would.

    as Balena Etcher or whatever dont supply .desktop files.

    https://imgur.com/NUZiECs.png

    • rollingflower@lemmy.kde.social
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      Flatpak does this, just have a look. Every app has its config stored in its own directory. Apps only have access to that directory, if they dont get other static permissions.

      yes you could of course script that, but it doesnt change the problem with appimages having insecure updates. Flatpak uses OSTree, Android has a package manager that saves the signature and if that doesnt match, an update fails.

      you can add images inline with ![title](url)