Feature Request: CICD about rbw

[doy]

i would like to get ci of some sort set up for running tests, but i already have a release process that i'm happy with.

[onedr0p]

the debian packages i publish at https://git.tozt.net/rbw/releases/deb/ are binary packages - it should be straightforward to extract the binaries from them (this is what i was doing to generate the rbw-bin aur package when it existed, for instance).

To be fair it's also pretty straight forward to set up a GitHub workflow to attach debs, rpms and the static binary (and support different architectures!) to github releases. Why not solve the problem for everyone and learn something new in the process?

Github doesn't need to be the only place you support downloading the app but it's much easier than manually doing it every release on your personal git site. You have a mirror here, so you do see some benefit to GitHub already.

[fugkco]

@doy what's your current release process? Would you be opposed to uploading the binaries to GitHub releases? One thing that i don't like is that I have to build rbw if I want to upgrade it, I'd much prefer downloading a binary.

[doy]

i currently publish binary packages for arch linux and debian/ubuntu, as described at https://github.com/doy/rbw#installation . is there something else you would like?

[onedr0p]

Yes, it would be nice if you could post the binaries to this Github repo, or prove the static binary somewhere. Not everyone on Linux uses the AUR or Debian. Thanks.

[fugkco]

Forgot about this. Just the binaries would be nice on GitHub, or elsewhere.

[doy]

the debian packages i publish at https://git.tozt.net/rbw/releases/deb/ are binary packages - it should be straightforward to extract the binaries from them (this is what i was doing to generate the rbw-bin aur package when it existed, for instance).