Open regern80 opened 1 year ago
Hi, thank you for the suggestion.
I have no idea how to do this. Would that be a config file that needs to be written? If so, could you create a PR?
An appimage is almost equivalent of .exe but on linux. One makes the appimage executable and it then it just runs when executed. Here is my custom appimage for dead, you can extract, make it executable and try it out
I see, could you write the cli command you used to create it? Maybe we can add it as a CI run
Link to official Appimagetool
eg. deadd-notification-center.AppDir
This directory needs;
AppRun (which is scipt or symlink pointing to the executable binary, the script is better though)
.desktop file and an icon with name that matches the one in .desktop file
*Directories and files of the application like usr, bin and etc. Core dependencies directories and files can also be added to increase compatibility.
Run in a terminal:
[path-to-appimagepool] [path-to-.AppDir-directory]
this will output the appimage in the home directory. If there are any errors, suggestions will be presented in the terminal.
Make the appimage executable
The appimage (path-to-appimage) can be added to the autostart, to launch deadd with desktop.
Ok, just to clarify, what exactly you intend with this issue:
Cheers
Main aim was proposing appimage as one of official release formats for non arch users
The official releases binary still use deadd.conf but I had updated my configs to deadd.yml, that is why I thought it didn't respect user configs.
I'm on linux mint and use a custom appimage bundled using arch2appimage. It works okay and reads config from $HOME/.config/deadd just like one built from source. The binary provided as official release doesn't seem to respect user configs but appimage will