exportarr: init at 1.1.0

[azahi]

Description of changes

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, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 22.11 Release Notes (or backporting 22.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
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[mweinelt]

• This should be moved into pkgs/servers/monitoring/prometheus.
• What's up with all the short opts in ldFlags, isn't there something more readable?
• Why force a static build for Linux systems?

[azahi]

• This should be moved into pkgs/servers/monitoring/prometheus.

Agreed.

• What's up with all the short opts in ldFlags, isn't there something more readable?

-s and -w are linker flags, there are no verbose counterparts to them.

• Why force a static build for Linux systems?

I used this as a reference. But looking at it now, it would be preferable to use dynamic linking because Nix handles it very well.

I'll make a follow up PR later.