SkullHex2@lemmy.ml to Linux@lemmy.mlEnglish · edit-28 days agoAAAAlemmy.mlexternal-linkmessage-square19fedilinkarrow-up176arrow-down14file-text
arrow-up172arrow-down1external-linkAAAAlemmy.mlSkullHex2@lemmy.ml to Linux@lemmy.mlEnglish · edit-28 days agomessage-square19fedilinkfile-text
minus-squareBrianTheeBiscuiteer@lemmy.worldlinkfedilinkarrow-up20·1 year agoIf 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.
minus-squareeverett@lemmy.mllinkfedilinkarrow-up2·edit-211 months agoHappy 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!
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.
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 thesort -V
switch that fixes it!