aphorme: init at 0.1.19

[AnyTimeTraveler]

Description of changes

Add the small and fast program launcher called aphorme

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• 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/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 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.

---

Add a 👍 reaction to pull requests you find important.

[tomodachi94]

Lgtm (and builds on my machine). One thing though: To speed up future time-to-review, consider adding a testVersion test. aphorme --version appears to contain the version :)

[AnyTimeTraveler]

Lgtm (and builds on my machine). One thing though: To speed up future time-to-review, consider adding a testVersion test. aphorme --version appears to contain the version :)

Done :)

[tomodachi94]

Lgtm, thanks for this! (Might use this myself, seems useful 🙂)

[Aleksanaa]

Could you explain why you used your fork instead of the original one?

[AnyTimeTraveler]

Could you explain why you used your fork instead of the original one?

The original creator changed the app version in the Cargo.toml to 0.1.19 and then pushed that change without rebuilding the corresponding Cargo.lock. Nix-build complained about the dirty Cargo.lock and refused to build.
The release I made to my fork only adds one commit, which updates the Cargo.lock.

[AnyTimeTraveler]

I have been talking with the author and the next release is planned to be switched to the official repo, but there is no timeframe for when the next release will happen.

I will keep maintaining the Nix package either way, as they are not involved with Nix.

[AnyTimeTraveler]

Good news, everyone :)
I talked to the original author and the Cargo.lock has been pushed.
I just updated the buildscript to point to the original repo.

[tomodachi94]

Lgtm, thanks for this!