cortex-command-community-project: init at 6.2.2

[gileri]

Add Cortex Command Community Project.

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/)
• 25.05 Release Notes (or backporting 24.11 and 25.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
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[SigmaSquadron]

Thanks for packaging this game!

Please take a moment to review our Commit Conventions and reword your commits appropriately; their titles must follow very specific patterns as defined in our documentation. Don't forget to squash your intermediate/fixup commits.

I've left some additional review comments below.

[gileri]

Thanks for the comprehensive review @SigmaSquadron !
I've implemented your suggestions, and a couple more :

• Un-vendored the patch
• Better description

[SigmaSquadron]

Builds and runs, but I get a rm: remove write-protected regular file '/tmp/CCCP.RqFrk3aDP/Data'? message after running it. I'm not sure if that's intended. Still, seems alright for an init PR.

[gileri]

I don't have this warning when running it on either a pretty new/clean NixOS unstable, nor an Arch with Nix. I don't see what could cause this. Can you share your mount options if you have /tmp mounted separately ? When you run umask, do you get 0022 ?

I agree that even with this potential bug it could be merged, with it a standard session leaves behind about 40KiB of files in /tmp, not a huge deal.

Thank you for the quick review in any case !

[SigmaSquadron]

I have boot.tmp.useTmpfs set to true, so that must be it. Still, unlinking the folder should ideally be done by the compiled application, not by shelling out to `rm`.

[SigmaSquadron]

Waiting for CI...

[SigmaSquadron]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 400403
Commit: 617b982c46a149754cd3d415458118cbdbfd5259

---

x86_64-linux

✅ 1 package built:

• cortex-command-community-project

[SigmaSquadron]

Approved automatically following the successful run of nixpkgs-review.

[SigmaSquadron]

Thanks for your patience on this one. I was unable to merge it before, as I was not a committer for Nixpkgs.