docs/reference/commands/export.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 export[e]
 
[h2]synopsis[e]
 
[code]
mp export [--all] <setname>
[e]
 
[h2]description[e]
 
snapshots the current install state into [code]WD/sets/<setname>.set[e] -- a plain text file, one package name per line, sorted. by default only [code]requested[e] packages are written (the same flag [see name="reference/commands/prune"]prune[e] reads, [see name="reference/commands/list"]mp list --installed[e] marks); [code]--all[e] instead writes every installed package, requested or not.
 
no dedicated command is needed to CREATE a set beyond this -- the file itself is the whole mechanism, and [code]@setname[e] is recognized by [see name="reference/commands/install"]install[e]/[see name="reference/commands/reinstall"]reinstall[e]/[see name="reference/commands/remove"]remove[e]/[see name="reference/commands/update"]update[e] the same way [code]world[e]/[code]all[e] are, anywhere a package-name argument is accepted. hand-editing or hand-writing a [code].set[e] file works identically to one this command produced.
 
[h2]examples[e]
 
[code]
mp export myset
ok: exported 12 package(s) to /usr/mp/sets/myset.set (install with: mp install @myset).
mp install @myset      # elsewhere, or later, after wiping and rebuilding
[e]
 
[h2]see also[e]
 
[see name="reference/commands/install"]install[e], [see name="reference/commands/list"]list[e], [see name="reference/commands/prune"]prune[e].