Make a release / git tag

[bjornfor]

I'm packaging kalibrate-rtl for Nix/NixOS and would like to ask if you could make a git tag in the repo as an indication to downstream that "this is the version you should use".

Something like git tag -a -m "Version 1.0" v1.0 && git push --tags should do it :-)

[barjac]

+1

[Romeo-Golf]

+2

[drsn0w]

+3 packaging for Gentoo

[barjac]

+++ Again after 5 years! I am packaging for Mageia. We still have no actual release / tag, it's all guess work to know when to grab a commit and package an update.
Please please do something to help with this situation.

[steve-m]

Well, this started as an quick and dirty fork of the original kalibrate by simply patching the UHD driver, and a proper "release" was never planned, because the right way of doing it would be of course to add the various SDR drivers into one unified kalibrate. This never happened..

If that helps I can add a tag. But while we are at it: how are you dealing with the other forks of kalibrate like kalibrate-lms and kalibrate-bladeRF etc.? I took a look at them, and they all use "kal" as name for the output executable as well. Do you rename that in your make install wrapper? Or should we change it to something like kal-rtl here?

[bjornfor]

In nixpkgs there are currently two kalibrate* packages, and their binaries are:

$ ls -1 $(nix-build -A kalibrate-rtl)/bin
kal

$ ls -1 $(nix-build -A kalibrate-hackrf)/bin
kal-hackrf

The hackrf one gets renamed s/kal/kal-hackrf/ in postInstall in nixpkgs, whereas the rtl one has no postInstall tweaks.

I have no opinion on whether to rename upstream or downstream, or just keep it as is.