ZeroHora 20 points 3 years ago

path: 0 5693990, hotness: undefined, score: 20, children: 1

isVeryLoud 6 points 3 years ago

Definitely the correct answer.

It's a drag and drop appimage manager, like macOS DMGs. And it's a flatpak!

path: 0 5693990 5702908, hotness: undefined, score: 6, children: 0

coolmojo 14 points 3 years ago

You can use AM or AppMan. It is a command line tool for managing AppImages. Including download , install, update and remove.

Have a look at

https://portable-linux-apps.github.io/

It is also open source.

save

path: 0 5693577, hotness: undefined, score: 14, children: 3

stepanzak 2 points 3 years ago

I tried AM some time ago, and I was extremely confused about the documentation and how to use it. I even watched a YouTube video from DistroTube on how to use it, but I still couldn't figure it out. I don't exactly remember the issues, though, and I hope it's better now.

save

path: 0 5693577 5696700, hotness: undefined, score: 2, children: 1

coolmojo 2 points 3 years ago

I am using AppMan as it does not require root and it does install the files into my home directory. It uses query parameter instead of search, but the install, update and remove are similar to the apt commands for example. I use AppImages when there is no package in the repository (or only older version) and it is not available as a Flatpak.

save

path: 0 5693577 5696700 5698896, hotness: undefined, score: 2, children: 0

coolmojo 1 point 3 years ago

save

path: 0 5693577 5698880, hotness: undefined, score: 1, children: 0

DangerousInternet 13 points 3 years ago

save

path: 0 5693623, hotness: undefined, score: 13, children: 2

BrianTheeBiscuiteer 20 points 3 years 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.

save

path: 0 5693623 5694142, hotness: undefined, score: 20, children: 1

everett 2 points 3 years 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!

save

path: 0 5693623 5694142 5719267, hotness: undefined, score: 2, children: 0

Ropianos 10 points 3 years ago

There is also AppImage Launcher which works nicely for me. It automatically integrates AppImages into the DE (e.g. search and start menu) and a few other nice things.

https://github.com/TheAssassin/AppImageLauncher

save

path: 0 5696272, hotness: undefined, score: 10, children: 0

avidamoeba 6 points 3 years ago

Use a package management system that supports this use case.

save

path: 0 5697291, hotness: undefined, score: 6, children: 0

Gecko 5 points 3 years 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 ^^"

save

path: 0 5696425, hotness: undefined, score: 5, children: 1

SkullHex2 1 point 3 years ago

save

path: 0 5696425 5698156, hotness: undefined, score: 1, children: 0

Atemu 4 points 3 years ago

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

save

path: 0 5697894, hotness: undefined, score: 4, children: 2

SkullHex2 1 point 3 years ago

save

path: 0 5697894 5698197, hotness: undefined, score: 1, children: 1

Atemu 4 points 3 years 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.

save

path: 0 5697894 5698197 5699002, hotness: undefined, score: 4, children: 0

warmaster 4 points 3 years ago

What's wrong with gear lever?

save

path: 0 5695111, hotness: undefined, score: 4, children: 1

Archr 3 points 3 years 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.

save

path: 0 5695111 5699574, hotness: undefined, score: 3, children: 0

Max_P 4 points 3 years ago

Isn't that kind of AppImage's whole thing, to behave like Mac apps that you just double click on regardless of where they are, and not have a package manager?

I'd go for the Flatpak if you want it to be managed and updated.

We went from distro packages to Flatpak to bare files and circling back to reinventing the package manager...

save

path: 0 5719380, hotness: undefined, score: 4, children: 0

Pantherina 3 points 3 years ago

I am a big fan or repackaging Appimages as Flatpaks, with appstream metadata, sane package management (not the windows way or simply nothing at all), sandboxing and desktop entries.

There are some repos on Github that do that.

https://github.com/...

save

path: 0 5701185, hotness: undefined, score: 3, children: 0

free 2 points 3 years ago

I just have a keybind to open file manager of the app images 🤷

save

path: 0 5705514, hotness: undefined, score: 2, children: 0

Rules

Related Communities

Rules

Related Communities