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

Support AppImages #86

Closed
saulrh opened this issue Jan 10, 2025 · 4 comments
Closed

Support AppImages #86

saulrh opened this issue Jan 10, 2025 · 4 comments

Comments

@saulrh
Copy link

saulrh commented Jan 10, 2025

.AppImage isn't a recognized extension, so even though this would absolutely run on my machine, it's not a candidate. AppImages, being single executable files that contain an entire program, seem like exactly what this project wants to support. For an example of a project that releases only AppImages, see https://github.com/hzeller/timg/releases/tag/v1.6.1.

This might require an additional flag for choosing a new name for the executable being downloaded - I'd want this to land on my disk as timg, not timg-1.6.1-x86_64.AppImage.

@autarch
Copy link
Member

autarch commented Jan 11, 2025

Yes, adding the extension would be easy. I think maybe we would need a --rename-exe arg to support renames. This could work for any sort of executable, though.

@saulrh
Copy link
Author

saulrh commented Jan 17, 2025

Having a general-purpose --rename-exe arg would certainly be useful for other formats, agreed. "I want eza to land in my bin dir as ls", "I want to deconflict different versions of the same app", etc.

Should I split that out into a separate issue?

@autarch
Copy link
Member

autarch commented Jan 18, 2025

Hmm, now I'm remembering how ubi's behavior is kind of weird, where it actually already renames the executable in some cases. But this --rename-exe feature is still useful.

@autarch
Copy link
Member

autarch commented Jan 18, 2025

Support for AppImages and the --rename-exe-to flag are both in v0.4.1.

@autarch autarch closed this as completed Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants