Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Option to specify the output directory when using --appimage-extract #1214

Open
IamPhytan opened this issue Sep 19, 2022 · 2 comments

Comments

@IamPhytan
Copy link

IamPhytan commented Sep 19, 2022

Hello,

I am wondering if there could be a way to specify the path in which AppImage files are extracted. For example, say I want to reuse a desktop entry from an AppImage :

$ ./example.AppImage --appimage-extract example.desktop -o ~/.local/share/applications/
@TheAssassin
Copy link
Member

TheAssassin commented Sep 19, 2022

Why not use something like this?

orig_cwd="$PWD"
cd ~/.local/share/applications/
"$orig_cwd"/example.AppImage --appimage-extract example.desktop
mv squashfs-root/example.desktop .
rmdir squashfs-root

@IamPhytan
Copy link
Author

Yes, it could kinda work.

So, if I understood, let's say we also want to retrieve the icon, we would do this ?

orig_cwd="$PWD"
cd ~/.local/share/applications/
"$orig_cwd"/example.AppImage --appimage-extract example.desktop
mv squashfs-root/example.desktop .
rmdir squashfs-root

cd ~/.local/share/icons/
"$orig_cwd"/example.AppImage --appimage-extract example.png
mv squashfs-root/example.png .
rmdir squashfs-root

Or, we could do this, but we should take in account that the AppImage is inside a folder on which the user has permissions ?

orig_cwd="$PWD"
"$orig_cwd"/example.AppImage --appimage-extract example.desktop
"$orig_cwd"/example.AppImage --appimage-extract example.png

mv squashfs-root/example.desktop ~/.local/share/applications/
mv squashfs-root/example.png ~/.local/share/icons/
rmdir squashfs-root

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants