4 ms·

Thanks for the answer! Looking forward to the followup post :D And yeah, nix naming conventions are sometimes a mess. Your approach does seem much nicer. Last

Thanks for the answer! Looking forward to the followup post :D And yeah, nix naming conventions are sometimes a mess. Your approach does seem much nicer. Last question if you have a bit more time. How come that you don't have every version of a package available? Is it because you only parse the Hydra stable 23 builds (which I guess aren't updated on every version) or because you parse them only periodically like Lazamar's Nix Package Versions?

jljljl 3y ago
We're parsing periodically (though our index is more up to date than Nix Package Versions at the moment). We've also truncated pre-Flakes commits, though we are planning to include those in the future
- nathan_phoenix 3y ago
  Looking forward to that for completeness sake! Btw, regarding a bit older pre-Flakes commits, at least some packages will error out while nix-installing on M1 (or newer) macbooks because at that point nix packages didn't anticipate macbooks ever ditching x86 for aarch... Hope this info helps you out, at least took me some time to realize that the random obscure error was caused by this. Can be almost always fixed by appending "--system darwin-x86_64" to the nix command to use Apple's Rosetta binary translation, cheers.