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
      8·
      1 year 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
        1·
        1 year 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!

    • Archr@lemmy.world
      2·
      1 year ago

      The issue with gear lever is that not many people know that it exists. I only started using it a few months ago and I’ve been on Linux for the better part of the last decade.

  • Gecko@lemmy.worldEnglish
    51·
    1 year ago

    Not to be that person but I’m curious what made you go with AppImage over Flatpak, given that you already mentioned using the Flatpak as an alternative ^^"

  • Atemu@lemmy.ml
    41·
    1 year ago

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

      • Atemu@lemmy.ml
        3·
        1 year 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.