Publish binaries to github releases

[Rigellute]

Thank you for this tool!

Are you interested in publishing prebuilt binaries to github releases? If so, I could potentially help setup the github actions to build binaries when you push a git tag.

[Stargateur]

that doesn't look very useful for a tool that should be installed with cargo anyway.

[Canop]

Bacon is one of the few programs for which I don't provide binaries, because any potential user has a rust compiler and is more at ease with using cargo install than downloading binaries.

I'll reconsider if some user tells me he would need precompiled binaries and explains why.

[Rigellute]

My use-case is that I mostly use cargo binstall these days to avoid building from source or manually installing binaries. But totally understand if it's not a priority for this project.

[Canop]

@Rigellute This makes sense. I didn't knew binstall.

[Canop]

Is there a free solution for generating mac binaries in github actions ?

[Stargateur]

open source project can run github action on mac for free, I don't know any limit but I guess github set some, so I expect you could just compile it using a mac os in the github action. For private reposition there is this doc https://docs.github.com/en/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions about minute count but as I said it should be fine for public repo as long as it's fair use.

[Rigellute]

Yes, github actions will be free for this project.

If you want to try this yourself, I recommend using cargo-dist, which massively streamlines all the steps of providing prebuilt binaries for a rust project

[Canop]

A problem I have with pushing tags to create binaries in GitHub is that it gets messy, like many GitHub actions, because you push the tag, wait half an hour for it to be finished, see that it failed, try some changes at random, etc.

And I know by experience that cross compiling fails a lot, especially in Rust.