-
Notifications
You must be signed in to change notification settings - Fork 257
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
AppImageLauncher Lite #178
Conversation
It just says
instead of running. As I need to to turn this into an ExtensionImage, how can I use it without the |
As a user, I would not understand why it is called |
Is AILL using |
Help text has been fixed already, but forgot to push. Dunno how your weird ExtensionImages work. You can just call
Might be because we still use libappimage 0.1.x due to stability issues on main branch. Switch is planned for next weeks. That's really a minor thing to add, though. I'd rather settle on stability for now.
Why the heck is there anything filled in anyway? It should be empty, and use the default value (which is
This should be force-checked cosmetically, actually. AIL Lite's only configuration possibility is the main applications dir path. And that's also nothing you'd have to change regularly.
It could, but there is no point in doing so, at least for now. The only purpose of the filesystem is to bypass |
Exactly like an AppImage, with the exception that they are mounted during boot and stay mounted all the time, and They are not "weird". They are to the system what AppImages are to apps. |
Why not just call |
That'd be an option, yes. Right now I'm just trying to find out how stuff works and what does what. If |
@probonopd well why not, I didn't invest overly much time to optimize everything to the max. It's not used, as you can see from the AppRun script. |
System doesn't like the magic bytes. Replace them and things will work. Nothing specific to AIL Lite. Please only post information relevant for AIL Lite. I want to merge this. E.g., your SystemImageKit has no relevance for this project (more a nice to have for you, but doesn't really provide information whether AIL Lite does what it's supposed to do). |
As in: I cannot run any AppImages?! |
Well, you haven't believed me at least since early 2018 that newer systems don't like the magic bytes at all any more. Many Docker systems were affected already, so we had to tell people to just cripple AppImages by removing the magic bytes. |
With |
It still has the binfmt stuff in the AppImage, this hurts when converting to an ExtensionImage. Removing it makes it work for me. |
May I ask that the scanning of the other partitions is added? Then it becomes usable for me. |
That stuff is not installed in any way! It can't be that. It's impossible!
One thing after another. |
|
Well that's some very special treatment you request. Following your off-GitHub explanations you just overlay-mount the AppImage on the system and hope for the best... |
Try the latest build please. |
Taken care of in https://github.com/probonopd/SystemImageKit/blob/d210f327a08b63362e5787876dc279e0b7b6cae8/boot/bin/generate-aill-extension#L90-L97 as well, with that it is running. |
I guess you missed 52609f9 then? |
AppImageLauncher Lite is an alternative way to install AppImageLauncher. It's a no-root-required version that is shipped as an AppImage and can be installed from the CLI.
NOTE: The recommended and most powerful installation method is still to use the native packages! This is just an alternative for people who can't afford using
sudo
. It lacks many useful features.I selected the most useful features of AppImageLauncher that can be installed and managed without access to root:
~/Applications
(or any other dir you choose for your apps)You can install the AppImage by calling it via CLI with
install
(and remove it withuninstall
).TODO:
@probonopd @azubieta please test, AppImage available e.g., here.
Fixes #161.