Skip to content
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

Cut release, so distributions can ship #59

Closed
dvzrv opened this issue Aug 7, 2018 · 5 comments
Closed

Cut release, so distributions can ship #59

dvzrv opened this issue Aug 7, 2018 · 5 comments

Comments

@dvzrv
Copy link

dvzrv commented Aug 7, 2018

For this software to be shipped somewhere on Linux distributions, you'll need to cut a release! :)

@jesseduffield
Copy link
Owner

How to do binary releases is a topic I am very unfamiliar with. Could I get some pointers (or perhaps @dawidd6 could chip in)

@dawidd6
Copy link
Collaborator

dawidd6 commented Aug 7, 2018

I think that @dvzrv by release meant just a git tag.

Binary release as you say can be nothing more than a github release (git tag) with binaries for various OSes attached, since Go is statically linked it should be straightforward.

@dvzrv
Copy link
Author

dvzrv commented Aug 7, 2018

@jesseduffield Yes, I meant a git tag with that. Downstream distributions will have their own way of packaging your software anyways (maybe even using their very own way of building/packaging go applications).

@jesseduffield
Copy link
Owner

I've hooked up travis CI to deploy tagged releases. Does this fix the original issue? Or is there more work to do?

@jesseduffield
Copy link
Owner

Closing cos it looks like we're good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants