Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
appimages [21.02.2021 08:14] – [AppImageLauncher] Pascal Suter | appimages [21.02.2021 10:22] (current) – [Appimaged] Pascal Suter | ||
---|---|---|---|
Line 21: | Line 21: | ||
==== Appimaged ==== | ==== Appimaged ==== | ||
- | [[https:// | + | [[https:// |
- | what I don't like about it, it also searches your Downloads directory, to basically | + | what I don't like about it is, it also searches your Downloads directory, to detect an app image as soon as its downloaded. This is of course very convenient, however, it makes your system a mess! also keep in mind, that it automatically marks everything executable. |
- | Of course i can manually copy them to a different folder, but there we ware, i need to open a file browser again and start to manage my appimages. | + | here is a list of all directories that are searched for appimages, out of the source of [[https:// |
+ | <code go> | ||
+ | var candidateDirectories = []string{ | ||
+ | xdg.UserDirs.Download, | ||
+ | xdg.UserDirs.Desktop, | ||
+ | home + "/ | ||
+ | home + "/ | ||
+ | home + "/ | ||
+ | "/ | ||
+ | "/ | ||
+ | } | ||
+ | </ | ||
- | also I think appimaged itself needs some attention, as in placing | + | Sadly there is no configuration option that would allow us to change the directories in which appimages are searched, and looking at a comment from the developer to a request of a user to have a configuration option to disable the automatic creation of the Applications folder, he answered saying, that configurability adds complexity and he wants to avoid that.. a valid thaught, however, it does not help in this case. I personally believe that configurability does not need to add complexity, as long as everything runs with good default settings. but that's an opinion just like any other ;) |
+ | |||
+ | === Installation === | ||
+ | To install | ||
+ | |||
+ | It is important that you copy it first to the location where you want to keep it, as it will link to itself in the systemd service it creates. So if you run it the first time from your download folder, it will link to there and as soon as you clean up your downloads the next time, appimaged is gone! A good location for appimaged would bi in '' | ||
+ | |||
+ | if you have started appimaged already from a folder where you didn't want it to stay, simply stop the systemd service | ||
+ | systemctl --user stop appimaged.service | ||
+ | then copy the appimage file to the defintive location and start it from there, it will automatically re-create the systemd entry | ||
+ | |||
+ | === uninstallation === | ||
+ | unfortunately this is not documented yet on the appimaged github page. in order to remove it, you have to do three things: | ||
+ | |||
+ | 1.) stop and disable the systemd service | ||
+ | systemctl --user --now disable appimaged.service | ||
+ | 2.) remove the service (if you want to tidy up your system again) | ||
+ | rm ~/ | ||
+ | 3.) delete the appimage of appimaged :) | ||
+ | rm path/ | ||
+ | 4.) remove all the entries it made in your launcher | ||
+ | rm ~/.local/ | ||
==== AppImageLauncher ==== | ==== AppImageLauncher ==== | ||
Line 46: | Line 78: | ||
if your appimage has embedded udpate information, | if your appimage has embedded udpate information, | ||
+ | |||
+ | === Uninstalling === | ||
+ | AppImageLauncher can be uninstalled via '' | ||
+ | rm ~/ | ||
+ | to remove a left over symlink from your system. you need to reboot before you can try to run appimaged | ||