-
Notifications
You must be signed in to change notification settings - Fork 156
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
Publish binaries on new release using CI #17
Comments
Hmm, I will need to research more into this when I have time. I am not very knowledgeable on CI. |
Another vote for this. This is an essential also if you're expecting people in low ressources platforms like the raspberry pi to try it out. It would also make it much easier to release this as a precompiled package for other distros. Many people dont have , dont want to have, the entire rust distribution , and the constantly updating 500 mega, just to quickly try it out and compare it to other existitng file managers in go or rust
Have you also heard about github actions ? Perhaps you can also have a look at how other cli rust tools do it, for example, skim, https://github.com/lotabout/skim/releases, ripgrep, https://github.com/BurntSushi/ripgrep or fd, https://github.com/sharkdp/fd |
Here's the actual diff where Github Actions was implemented for skim. I might take a shot at it if I get some time. |
So there's a cool project called trust that you can setup in your project, so that every time you create a new release/create a new tag, it will automatically build binaries for you using travis ci and publish them to the releases tab. This is really nice for people who want to use rust projects but don't want to have to deal with its compile times :D
edit: Looks like that project might be abandoned, but the idea is still the same. Ripgrep and Alacritty both do some sort of similar thing for their projects, so we could always check those out too.
The text was updated successfully, but these errors were encountered: