guix

A Guix package definition specifies source origins (url-fetch, git-fetch), inputs, native-inputs, propagated-inputs, build-system, and build-arguments. Start with a basic template, declare dependencies by type, set the source URL and license, then add custom build phases or patches as needed for your package.

Inputs are runtime dependencies, native-inputs are build-time only, and propagated-inputs are runtime dependencies that become inputs to packages that depend on yours. Correct classification ensures reproducible builds and prevents unnecessary dependency bloat.

System services use gnu/services modules for OS-level daemons and configurations, while home services use gnu/home/services for user-level environments. Both enable reproducible, declarative service definitions that can be version-controlled and deployed consistently.

Yes, work with a local Guix repository checkout to iterate on package definitions, run builds, and debug issues. Test against your build-system configuration and verify patches and phases execute correctly before integrating upstream.

Use custom build phases when the standard build-system workflow doesn't match your package's requirements. Phases let you modify source, patch dependencies, or adjust compilation flags—implement only the phases needed to override default behavior.

Migration typically involves updating input field names, adjusting build-system syntax, and modernizing source origin declarations. Expert guidance helps identify deprecated patterns and ensure compatibility with current Guix standards and build infrastructure.