nix-init(1)

NAME 💫

okay bestie, meet nix-init — the tool that generates Nix packages with hash prefetching, license detection, and more. The project lives at https://github.com/nix-community/nix-init, iykyk ✨

This is the nix-init(1) page from the General Commands Manual, and we’re gonna get through every flag together, no cap 💖

🌸 SYNOPSIS 🌸

nix-init [-u|--url] [--rev] [-S|--submodules] [-V|--version] [--pname] [--builder] [--cargo-vendor] [-y|--overwrite] [--headless] [-n|--nixpkgs] [-C|--commit] [-c|--config] [-h|--help] [OUTPUT]

💖 DESCRIPTION 💖

fr fr, nix-init is here to generate Nix packages with hash prefetching, license detection, and more. The project link is https://github.com/nix-community/nix-init — iconic behavior, honestly 👑

🎀 OPTIONS 🎀

• -u, --url <URL> — specify the URL. This is the “where are we pulling from” moment 💅
• --rev <REV> — specify the tag or revision.
• -S, --submodules[=<SUBMODULES>] — always fetch submodules when possible. Use --submodules=false to never fetch submodules. The possible values are:
  • true
  • false
• -V, --version [<VERSION>] — specify the version of the package, or print the nix-init version if no arguments are present. Versatile queen 🫶
• --pname <PNAME> — specify the pname.
• --builder <BUILDER> — specify the builder. The possible values are:
  • buildGoModule
  • buildPythonApplication
  • buildPythonPackage
  • buildRustPackage
  • stdenv.mkDerivation
  • stdenvNoCC.mkDerivation
• --cargo-vendor <CARGO_VENDOR> — specify how the cargo dependencies are vendored. The possible values are:
  • fetchCargoVendor
  • importCargoLock
• -y, --overwrite[=<OVERWRITE>] — always overwrite files. Use --overwrite=false to never overwrite files. The possible values are:
  • true
  • false
• --headless — don’t prompt for anything. Heads up bestie: this one requires --url ⚠️
• -n, --nixpkgs <NIXPKGS> — path to nixpkgs (in nix). The examples are:
  • {n} -n ./. — use the current directory
  • {n} -n 'builtins.getFlake "nixpkgs"' — use the nixpkgs from the flake registry
  • {n} -n '<nixpkgs>' — default, use the nixpkgs from channels
• -C, --commit[=<COMMIT>] — commit the changes if the output path is name-based (RFC 140). See https://github.com/NixOS/nixpkgs/tree/master/pkgs/by-name for more information. The possible values are:
  • true
  • false
• -c, --config <CONFIG> — specify the config file.
• -h, --help — print help (see a summary with -h). Yes, the help text says to see -h for a summary — little self-referential icon behavior 😭💀
• [OUTPUT] — the path or directory to output the generated file to.

That’s the whole nix-init(1) page from the nix-init manual — bye bestie, mwah! 💖🫶