old filename so to remove that file we pass the -r option. It overwrites it by default but also makes a backup file with. The -r option removes old appimage file and -O option overwrites the old file. So updating an appimage is this command appimageupdatetool -rO ~/store/Krita/nightly/krita-nightly One of the best advantages of using this tool is that it has the option to self update itself and also update the appimage file in place having the same name that you have given the appimage. I then mark it as executable with the following command. Make sure you have ~/.local/bin folder in your $PATH variable. The above command downloads the binary file of the tool to my computer’s local/bin folder. I downloaded the CLI version which is named appimageupdatetool. This tool has a GUI version and also a CLI version. When searching for a solution to automate this I found out about appimageupdatetool I believe this is the same tool that Krita uses in back-end to fetch the update. The update done from the Krita’s welcome screen downloads a file with new file name and we have to either adjust the name in desktop file or rename the downloaded file. I already have two different desktop files to launch the nightly and stable Appimage version of Krita. I rename the files of appimage to stable and nightly respectively so that it becomes each to point them to a shortcut and there is no need to change the desktop shortcut file always. Usually I used to click on the update button and then manually adjust the filename of the Appimage etc. So I thought that it is a cool idea to use script to automate the update process. When chatting on Krita IRC deevad mentioned that he uses a script to automatically download Krita nightly update and manage the launcher icons etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |