-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Flatpak package #2076
Comments
I can try to put together an AppImage. I'm new to both AppImages and Flatpaks but I'm happy to learn. Based on some quick research, AppImage seems like it may be the better choice since it's more self-contained. If anyone with more experience with these things has an opinion though, please weigh in! |
AppImages don't require any kind of installer, and I've found that aspect of it useful when using Neovim's AppImages. "Make it executable and run" is quite easy to do. I haven't used Flatpak so not much opinions there. |
AppImages seem to require a |
#283 has a brainstorm and there are a bunch of good ideas there but nothing chosen yet |
If you (somehow) embed the right metadata in the Appimage then you can use https://github.com/AppImage/AppImageUpdate to auto update it, pretty cool! It is still alpha software, but I am sure it will be fully working soon and it would be amazing to get auto-updating nightly releases at the press of a button :) |
I take it you're referring to this part of the spec? It seems like supporting that is pretty simple with the linuxdeploy appimage, I'll see what I can do! |
I'd like a Flatpak if possible. It's always really useful to have the option of an AppImage, but I like being able to update all of my apps from one place (ie. |
I packaged Helix as a flatpak. I wrote the appstream metadata myself, because I didn't find it anywhere. Also I made the package to work both on x86_64 and aarch64 by downloading corresponding archive from github releases. I didn't test it on aarch64 because I don't have the hardware. I don't see any reason why it wouldn't work but it's probably better to check. If everything is fine, then the only thing left to do is submit it to flathub. |
Just fyi on https://github.com/blt-r/helix-flatpak/blob/main/com.helix_editor.Helix.yml#L4 should this be 22.12 instead of 22.08 |
No, 22.08 is version of |
Oh makes sense sorry about that |
Helix is now available on Flathub.
|
Awesome, thank you! |
see base help with like Dart and Rust... And some other stuff and not clear on.... Could someone please help and guide me though a complete for C/C++ (and bash scrips maybe?) please help? Oh yes I am on Debian 12 x64 |
The flatpak is running inside of a container, which means it doesn't integrate with your host system and can't access executables installed on it. If you want helix to be integrated into your host system it's better to install it as a native package. If you want to set up helix flatpak to work with clangd you need to install flatpak sdk extension. There are instructions on how to do that in this file. You were supposed to see that file the first time you ran helix, but maybe you opened another file so that one was in a different buffer. |
Yea ok thank you... But I totally lost... I do not know rust nor I'm in interested in.. But I still have to install cargo to use Helix? I is not understands what I have to do with flatpak to use Helix either. |
You don't need cargo to install helix. Read through that file, it explains how to add sdk extensions for different languages. To get clangd you will need llvm16 sdk extension. Or find a way to install helix natively, so you can use clangd installed on your host system. |
Discussed in #1968
Originally posted by martincalveira April 5, 2022
Hi!
Is it on the roadmap to create an Appimage or Flatpak package?
Thank you.
The text was updated successfully, but these errors were encountered: