I have a particular question. When making a pr to nixpkgs, what is common practice? Do I fork master and then PR straight to it? Is there a branch to submit to first? In addition, I’m a noob who would love to know what a .patch file is. Is it just a documentation of the patch? Is it actually code? It looks like a git diff. I understand the patch was to nix, and not nixpkgs, so is it just a diff of that change?
Edit: ok so my first question has been answered very thoroughly thank you I somehow forgot to check contributing.md
Git has powerful functionality for sending your changes (PRs) as files. For example, you can do git diff > my_changes.patch, send it to someone, and someone could apply all your changes by git apply my_changes.patch
This is because Linus Torvalds (the creator of Linux) created git specifically for Linux kernel needs. And they still use email to send changes. Don’t know anything more about it, but I am sure you can google it.
Where do I find documentation on the nix C++ headers things like this imports to define things like new primops which im assuming means builtins? Is there docs or is it just source code in the nix package manager’s repo? Theres only like 1 short paragraph on it in the manual that I couldnt make heads or tails of.
Ah. All good. Well if anyone knows, I am all ears, I wanna make a builtin and learn how all this REALLY works. But yeah thank you so much you just answered questions I didnt know I had