npingler-build(1)

πŸ“¦
version 0.6.0 Β· 2 versions
, in nixpkgs unstable

πŸŽ€ npingler-build(1) β€” bestie edition πŸŽ€

okay so real quick: this is from the General Commands Manual, section 1, and the page name is npingler-build. got it? good. let's go πŸ’…


✨ NAME ✨

npingler-build β€” build the current profile but don't switch to it 🫢

like, you're doing the homework but you're not turning it in yet. iconique behavior honestly.


✨ SYNOPSIS ✨

npingler build [--hostname] [--profile] [--diff-derivations]
[--pin-registry-root] [--root-registry-path] [--pin-channels-root]
[--root-profile] [--extra-nix-args] [--extra-nix-build-args]
[--extra-nix-eval-args] [--extra-nix-env-set-args] [--config] [--file]
[--log-filter] [--debug] [-v|--verbose] [--dry] [-h|--help]

✨ DESCRIPTION ✨

Build the current profile but don't switch to it.

no cap, that's the whole vibe: it builds. it does not switch. those are two different things and honestly the distinction is doing a lot of work here 😌


✨ OPTIONS ✨

  • --hostname <HOSTNAME> β€” the hostname you're building the configuration for πŸ–₯️ this maps to the npingler.${hostname} output attribute in your flake, iykyk. you can also set it with the HOSTNAME environment variable.
  • --config <CONFIG> β€” path to the config file you wanna use. defaults to ~/.config/npingler/config.toml πŸŽ€
  • --file <FILE> β€” path or directory that contains your npingler Nix expressions. defaults to whatever the --config directory is πŸ“
  • -h, --help β€” print help (see a summary with -h). the short one is the tl;dr version bestie πŸ’–

✨ NIX PROFILE OPTIONS ✨

  • --profile <PROFILE> β€” the profile to use for nix profile operations. may also be specified with the NIX_PROFILE environment variable 🌸
  • --diff-derivations <DIFF_DERIVATIONS> β€” a command, like nix-diff or nvd, that you use to diff derivations πŸ‘€ this gets executed so you can see a diff of the changes being made to your profile before it builds. it may contain shell-quoted arguments (so yes, you can be fancy with it).

✨ NIX REGISTRY OPTIONS ✨

  • --pin-registry-root <PIN_REGISTRY_ROOT> β€” pin Nix Flake registry entries for the root user πŸ‘‘ [possible values: true, false]
  • --root-registry-path <ROOT_REGISTRY_PATH> β€” the Nix Flake registry path for the root user. defaults to /etc/nix/registry.json. may also be specified with the ROOT_NIX_REGISTRY environment variable πŸ—‚οΈ

✨ NIX CHANNEL OPTIONS ✨

  • --pin-channels-root <PIN_CHANNELS_ROOT> β€” pin Nix channels for the root user ✨ [possible values: true, false]
  • --root-profile <ROOT_PROFILE> β€” the root user's Nix profile path. defaults to /nix/var/nix/profiles/per-user/root/channels. may also be specified with the ROOT_NIX_PROFILE environment variable 🧚

✨ NIX COMMAND ARG OPTIONS ✨

  • --extra-nix-args <EXTRA_NIX_ARGS> β€” extra args for nix invocations. this is for all nix binary ("nix3") invocations, but it does not apply to (e.g.) nix-env πŸ’€
  • --extra-nix-build-args <EXTRA_NIX_BUILD_ARGS> β€” extra args for nix build invocations. note this is NOT for nix-build, which we do not invoke 🚫
  • --extra-nix-eval-args <EXTRA_NIX_EVAL_ARGS> β€” extra args for nix eval invocations πŸ”
  • --extra-nix-env-set-args <EXTRA_NIX_ENV_SET_ARGS> β€” extra args for nix-env --set invocations 🎯

✨ LOGGING OPTIONS ✨


πŸ’œ reminder from your girl: --dry means genuinely nothing changes. it's giving "window shopping". don't come for me if you expected it to write stuff, because it will not.

slay, that's the whole page πŸ¦‹ this was build (the version/source bit, as printed down there in the footer) and it's dated npingler-build(1) β€” okay that part is just the manual reference, but the footer literally reads build on the left and npingler-build(1) on the right, so there ya go. go build your profile without switching to it, bestie. proud of you. periodt πŸ’–πŸŽ€πŸŒˆ

πŸ“¦ where this page comes from