zigmod: init at 90

[paveloom]

Description of changes

A package manager for the Zig programming language (https://github.com/nektro/zigmod).

Note: it's gonna be broken on Darwin until Zig 0.10.1 is fixed.

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/)
• 23.05 Release Notes (or backporting 22.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.

[paveloom]

Result of nixpkgs-review pr 217229 run on x86_64-linux 1

1 package built:

• zigmod

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/prs-ready-for-review/3032/1850

[SuperSandro2000]

Please do not paste immediately on discourse.

[paveloom]

I've added a script that generates the list of dependencies.

[paveloom]

I've rewritten the package to take advantage of fixed-output derivations. I've also added a function to build Zigmod packages and a test for it.

[AndersonTorres]

LGTM.
Very complex, but LGTM.

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/prs-ready-for-review/3032/2322

[paveloom]

I've added a requirement to specify lockFile and manifestFile (as sources) in the buildZigmodPackage function. This way, we can avoid unnecessary builds of the fixed-output derivations for dependencies.

[SuperSandro2000]

that url scheme looks rather od. Is file:/// always there? Then we should move the logic into buildZigmodPackage

[paveloom]

No, it can be any scheme. I just use this one for the test. We separate updates of the package and the dependencies now, so the sources of lock and manifest files might be different. I imagine most of the time links to these files should be links to their blobs (contents of the file) from a specific commit.

[SuperSandro2000]

I've added a requirement to specify lockFile and manifestFile (as sources) in the buildZigmodPackage function. This way, we can avoid unnecessary builds of the fixed-output derivations for dependencies.

but name still contains version, so the FOD hash would still be wrong, we just wouldn't notice it, right?

[paveloom]

but name still contains version, so the FOD hash would still be wrong, we just wouldn't notice it, right?

Oh, right. I will just remove the version then.