-
-
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
Generate a .deb file #12453
base: master
Are you sure you want to change the base?
Generate a .deb file #12453
Conversation
Brilliant! I tried it on Debian Trixie and it worked perfectly, desktop and bash completion work great. I used a fresh VM that had not had Rust or Helix on it, installed Rust and The only problem seems to be the error messages regarding the grammars. They all seem to be working/present and correct inside
PS Debian is built for Trixie officially and just waiting in the new queue before it passes into testing: https://salsa.debian.org/debian/hx |
Yeah, this only LOOKS scary. It would be suppressed by adding It is late for me here, but if I have some time tomorrow, I will make another commit to the workflow to really have the .deb generated during the release process. |
Well, the recommended way is to But for some reason, maybe some maintainer can explain here to me, in the official release workflow helix/.github/workflows/release.yml Line 159 in 917174e
helix doesn't use this --profile opt , I wonder why. Is it not recommended anymore? If not, it should be taken out of the manifest and the building-from-source.md
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice addition to what all ready exists.
Thanks for making cargo deb
possible.
This PR makes it possible to generate a fully working .deb file with a one line command, thanks to
cargo-deb
which is a prerequisite for running it.The .deb integrates well into a debian/ubuntu based system
Tested installing in a VM on Mint21.3 and all looks well!
If the maintainers agree, a
cargo-deb
could be added to the release workflow to generate the .deb.