update blink and add related tool sipclients3

[charlieshanley]

Motivation for this change

Blink and sipclients3 are packaged on behalf of NGI as a Summer of Nix deliverable.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• 21.11 Release Notes (or backporting 21.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[charlieshanley]

Related issue about blink not running that will hopefully be fixed here: #85242

[SuperSandro2000]

disabled is normally ordered after version.

[SuperSandro2000]

Suggested change

	rev = "8209f3334c9b603fc81509333c38909755f663db";
	rev = version

[charlieshanley]

In this case I want a commit (specifically this one) that was made after the most recent tag, which is 3.0.3 .

[SuperSandro2000]

Than we can't tag this as the version number. Can you just fetch that commit as a patch?

[charlieshanley]

disabled is normally ordered after version.

Changed.

[charlieshanley]

@SuperSandro2000, thank you for the review!

I committed most of the changes you requested. What remains outstanding are the issues with missing tags and/or version numbers not reflecting commits we need in the upstream repos.

As I mentioned in another comment, I have contacted them about that. If upstream does not respond immediately, shall we proceed by removing reference to version numbers that are arguably misleading (IE use only the commit hashes)?

[jonringer]

Please follow CONTRIBUTING.md and manual#submitting-changes-making-patches and squash the fix-up commits.

git rebase -i is a powerful command which achieves this, I created a small video demonstrating it's use here. A more indepth text tutorial can be found here

[jonringer]

Also since you have a lot of packages being added. It might be easier for you to cherry-pick a lot of these into other PRs. Adding individual packages is a lot easier for both the reviewers and contributors

[charlieshanley]

Closed in favor of PRs for individual packages.