Authoring recipes
A recipe describes one source package — how to build it, how to split its outputs, and how the build farm should detect new upstream versions. Two files, four TOML sections.
ConceptHow peipkg-build invokes build.sh, what environment it gets, and how to write one for autotools, cmake, meson, or anything else.
How-toHow to split one upstream's build output across several .peipkg files (runtime, -dev, -doc), how the file-glob partition works, and the same_build dependency shorthand.
ConceptHow to declare what your package needs — runtime dependencies, optional dependencies, conflicts, virtual provides, and side-effect tools that run at install time.
How-toHow [upstream] and [watch] sections tell peipkg-manager where source lives and how to recognise new versions, so the recipe stays stable while versions roll forward automatically.
How-toHow to document your package's registry keys so regman can explain them. You ship a .regman fragment in /usr/share/regman/; this is its fenced format, the fmt/lint workflow, and the rules the tools won't catch for you.