> goes down the rabbit hole of the origin of "legacyPackages" naming

> finds no good reason (yada yada nested package attributes and nix flake show whatever) that would ever allow it to be properly addressed in #nixpkgs, the one package set most people will always have to interact with

> decides to refer to upstream #nix as legacyNix because it makes just as much sense

> goes down the rabbit hole of the origin of "legacyPackages" naming

> finds no good reason (yada yada nested package attributes and nix flake show whatever) that would ever allow it to be properly addressed in #nixpkgs, the one package set most people will always have to interact with

> decides to refer to upstream #nix as legacyNix because it makes just as much sense

Furthermore, Tenacity is now in #Nixpkgs unstable for macOS on both Intel and Apple Silicon! This complements the existing Linux ports on Nixpkgs 25.05 that run on both x86 (32- and 64-bit) and ARM (64-bit only).

The takeaway? Tenacity runs everywhere, and where we lack in official binaries, we are privileged to have an awesome community fill in the gaps! 😄

Furthermore, Tenacity is now in #Nixpkgs unstable for macOS on both Intel and Apple Silicon! This complements the existing Linux ports on Nixpkgs 25.05 that run on both x86 (32- and 64-bit) and ARM (64-bit only).

The takeaway? Tenacity runs everywhere, and where we lack in official binaries, we are privileged to have an awesome community fill in the gaps! 😄

@quillmatiq this looks fantastic! Can't believe there isn't a module, not even a package yet in #NixOS #nixpkgs
Looks like I got something to hack on once I get around to it ☺️

EDIT: looks like they ship a Flake, package and module upstream! 🤩

@bonfire