I have installed Bitwarden through its AppImage, and added a .desktop file to run it easily (and also to use a themed icon). Unfortunately, each time an update comes out, I need to manually update the file since it points directly to the older version

is there anything that can be done about this? I know of AppImageLauncher but I don’t like it, I’d rather install the Flatpak for Bitwarden if that’s the only solution. Another possible approach would be to have a script continuously running in the background, checking if the file Exec points to still exists… but that imho is not very clean.
Do you have any insight?

  • Atemu@lemmy.ml
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    11 months ago

    Don’t. Use a proper package manager for permanent installation of things. There’s a reason we have those.

    • SkullHex2@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      11 months ago

      Okay but… what would be the use case of AppImages then? Portability?

      • Atemu@lemmy.ml
        link
        fedilink
        arrow-up
        4
        ·
        11 months ago

        That and ease of deployment.

        If you as a developer wanted a non-technical user to test a thing you fixed for them, you could ask them to try an AppImage from your CI pipeline and they would easily be able to install it. They’re great for that.

        Also, trying out a package can leave unwanted system state around in traditional imperative system package managers. AppImages OTOH are self-contained and user-installable.