do not edit — generated by btf.
git.druid.rocksindexdruid520mpdocs/reference/index.btft

docs/reference/index.btft


[table class="topnav"]
[tr]
[td class="logotab"]mp[e]
[td][see name="index"]index[e][e]
[td][see name="guide/index"]guide[e][e]
[td][see name="reference/index"]reference[e][e]
[e]
[e]
 
[h1]reference[e]
 
the technical side of these docs: how mp itself is put together, and the deeper mechanics behind features the guide only shows the surface of. if you just want to use mp, see guide/index.html instead.
 
[see name="reference/architecture"]architecture[e] - the perl/c89 split, what each mplib module owns, the working-directory layout, and why a port's directory gets copied into a staging workspace at all.
 
[see name="reference/config"]config[e] - the narrative tour of mp's config-layering system (system, user, overlays, profiles, sysroots, the mp-managed overlay) and the patches.conf/hooks.conf conditional grammars. [see name="reference/mp-conf-example"]mp.conf.example[e], [see name="reference/patches-conf-example"]patches.conf.example[e], [see name="reference/hooks-conf-example"]hooks.conf.example[e], and [see name="reference/mpx-conf-example"]mpx.conf.example[e] (repo root) stay the exhaustive, copyable, key-by-key reference this page doesn't replace.
 
[see name="reference/multi-repo"]multi repo[e] - REPO_<name>=, priority ordering, per-repo branches, and how a single-repo setup differs on disk from a multi-repo one.
 
[see name="reference/extensions"]extensions[e] - adding a whole new mp <command> without touching src/ at all.
 
[see name="reference/slots"]slot[e] - resolve_slot's static+use-driven composition, the buildlink prefix wiring a slotted dependency gets automatically, and the revdep removal safety net.
 
[see name="reference/hooks"]hooks[e] - every pre_/post_<phase> boundary, the three ways to hook one phase, custom $MP_HOOK events, and sysroot isolation.
 
[see name="reference/commands/index"]commands[e] - one reference page per mp <command>, precise and complete (flags, exact behavior, examples) rather than the guide's narrative tour. rendered as man pages too (see testing.html's sibling doc, mk/dm.sh, for how).
 
[see name="reference/testing"]testing[e] - how the 18-suite regression tree and the deterministic fuzz suite work, and how to add a test of your own.
 
[see name="reference/pms-roadmap"]PMS roadmap[e] - concrete, source-grounded design notes for the real gaps against Portage's Package Manager Specification (repo-qualified atoms, USE-conditional atoms, slot operators/subslot rebuilds, transactional blocker resolution) -- what's missing, what closing it actually takes, and what's already correct by deliberate design rather than by accident.
 
[see name="reference/changelog"]changelog[e] - a curated history of the milestones that shaped mp, oldest first.
powered by btf.