docs/reference/commands/sync.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]mp sync[e]
 
[h2]synopsis[e]
 
[code]
mp sync
[e]
 
[h2]description[e]
 
pulls every configured repo (a single-repo setup's one [code]PORTS_DIR[e]/default clone, or every [code]REPO_<name>=[e] in priority order for a multi-repo one -- see [see name="reference/multi-repo"]reference/multi-repo[e]) and nothing else: no rebuilding, no resolution, no dependency graph. [see name="reference/commands/update"]mp update[e] runs this exact same step first, automatically, before it rebuilds anything.
 
a repo that's configured but not yet cloned locally gets cloned automatically on first run of ANY mp command (via [code]init()[e]), not just sync -- sync only matters for pulling in changes to a repo checkout that already exists.
 
fires the [code]pre_sync[e]/[code]post_sync[e] lifecycle hooks (see [see name="reference/hooks"]reference/hooks[e]).
 
[h2]examples[e]
 
[code]
mp sync
[e]
 
[quote class="note"]
note: after pushing a fix to a port and testing it against a running install/container, [code]mp sync[e] has to be run explicitly before [code]mp reinstall[e]/[code]mp install[e] will see it -- unlike [code]mp update[e], neither of those two syncs the tree on their own.
[e]
 
[h2]see also[e]
 
[see name="reference/commands/update"]update[e], [see name="reference/multi-repo"]reference/multi-repo[e].