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?

    • BrianTheeBiscuiteer@lemmy.world
      20·
      11 months ago

      If you’re taking a manual approach I would use a symlink:

      $ ln -s /path/to/stuff/Bitwarden.1.0.7.appimage /path/to/stuff/Bitwarden.appimage

      Then you can hang on to a previous version just in case, plus you can see from the original filename what version you’re on.

      • everett@lemmy.ml
        2·
        10 months ago

        Happy to hear if there are glaring problems with this approach, but if you can assume files named with version numbers, you can use a script to always launch the newest…

        #!/bin/bash
cd ~/Downloads
chmod +x $(ls | grep Appname.*AppImage$ | sort -rV | head -n 1)
./$(ls | grep Appname.*AppImage$ | sort -rV | head -n 1)

        Or you could change the script to sort by file modified date and launch the newest.

        edit: Discovered an issue with version numbering like .10 and learned about the sort -V switch that fixes it!