Script changes to Desktop
parkerlreed opened this issue · 5 comments
Why does the script change to desktop instead of using the script dir?
The script works into any directory you place it. I suggest to place it into a new directory before you run it.
Yes. My point was the script output goes to a folder I wasn't expecting.
I had no idea it was on desktop and had to bash -x the archimage script to notice.
https://github.com/ivan-hc/ArchImage/blob/main/archimage-cli#L24
Having a separate issue with building an appimage for qemu-full.
Just freezes after installing all the packages
(12/18) Updating fontconfig cache...
(13/18) Probing GDK-Pixbuf loader modules...
(14/18) Updating GIO module cache...
(15/18) Compiling GSettings XML schema files...
(16/18) Probing GTK3 input method modules...
(17/18) Updating icon theme caches...
(18/18) Updating the desktop file MIME type cache...
cp: cannot stat '': No such file or directory
The script I create is built on the desktop because for me it is easier to see it each time I create one, having a lot of directories opened when I work on my PC.
The error you faced is not related to where is created this script.
An AppImage to work needs a .desktop file and an icon in its root directory (the *.AppDir directory with the same name of your app).
qemu-full is a metapackage, there is no file in the package (see "Package content" at https://archlinux.org/packages/extra/x86_64/qemu-full/). Before you proceede with regular Arch Linux packages, be sure that there is a .desktop file, an icon and a binary in /usr/bin before you proceede with the creation of my scripts.
I've already talked about this into other two issues, #7 and #8 (comment)
So I can't use this for CLI programs? I want qemu-system-i386 to run when I call the Appimage. I gave that as a binary name. There will be no icon or desktop file for this.
No, you can't port this to an AppImage by default... but you can edit this script and add a .desktop file and an icon by yourself and change the AppRun into this script. All you need are the basic skills to write/edit a bash script. If you already use the command line on Linux for basic things like copy/move/remove files... this should not be a problem for you.
Alternativelly, install this using JuNest directly... and if you want to port this as an AppImage, study what is installed through the qemu-full metapackage and add your search results to the script.