nixpkgs

Create a reproducible nixpkgs derivation by defining build phases, nativeBuildInputs, and buildInputs within stdenv.mkDerivation, then resolve dependencies using callPackage to ensure consistent package composition.

The best way to override package dependencies in nixpkgs is by using override and overrideAttrs to modify existing derivations, or by applying overlays to inject custom package versions into the package set.

Package Rust or Python applications by leveraging language-specific nixpkgs builders like buildRustPackage and buildPythonPackage, which provide standardized build phases and dependency management for reproducible outputs.

Use overlays when you need to globally modify or extend the nixpkgs package set across multiple projects, whereas callPackage is better suited for local dependency resolution within a single derivation scope.

Yes, nixpkgs supports fetching sources from GitHub using fetchFromGitHub and other built-in fetchers, which compute hashes to ensure source reproducibility across different build environments.

Yes, you can customize build phases in stdenv.mkDerivation by overriding default phases like configurePhase or buildPhase, enabling tailored cross-platform packaging and specialized build workflows.