Pearl¶
- ID
pearl- Home page
- Platforms
🐧 Linux · 🍎 macOS
- Operations
installed·search·install·upgrade·remove- purl types
pkg:pearl- CLI name
pearl- Every call
pearl --no-confirm <command>- Issues and PRs
- Source
Pearl installs “packages” that wire dotfiles, shell and editor configuration into a machine (https://github.com/pearl-core/pearl).
A package is repo/name, the repository prefix being part of the identity
because several repositories can be configured at once. That is the form the
listings print and every verb accepts.
Parsing notes, verified against Pearl 2.3.12 on macOS:
--no-confirmis forced: Pearl asks “Are you sure?” before acting, and that flag is the documented way past it.Both listings are two-line records, the identifier then an indented description, so the patterns key on the identifier’s own shape and the four-space indent keeps the description out.
The inventory marks each entry
[installed], which is what separates it from the cataloglistprints without--installed-only.It carries no version anywhere, only an identifier and a description. That is a supported shape rather than a gap,
installed_versionbeing optional, and the same readingrustupandpyenvsettled.No
upgrade_all. Barepearl updateupdates Pearl itself, its help reading “Update Pearl or the packages if specified”, so only the single-package form is declared.
Caution
Pearl needs Bash 4.1 or newer and says so on every invocation when it does
not have it. macOS ships Bash 3.2, where installing fails inside the
package’s own hook functions while the read-only listings still work. A newer
Bash anywhere on PATH is enough: the whole round-trip was driven that way.
Note
An install runs the package’s own hook functions, which may take over the
terminal and may fail: a failing post_install rolls the package back rather
than leaving it half-installed.
What mpm adds to pearl¶
Through mpm, pearl gains --exact and --extended search, to narrow to exact names or match descriptions.
Bigger still, mpm reaches across every manager at once: mpm installed and mpm outdated cover pearl alongside every other manager you run in one table, mpm upgrade --all updates them together, and mpm sbom exports the whole machine as one bill of materials.
Every mpm command also gains --dry-run and --plan previews, cross-scheme version comparison and purl identifiers. See manager augmentations for how each one is built.
Your pearl commands, in mpm¶
You already know pearl: each operation maps one-to-one onto mpm, in an interface shared by every manager.
To… |
With |
With |
|---|---|---|
List what’s installed |
|
|
Search for a package |
|
|
Install a package |
|
|
Upgrade one package |
|
|
Remove a package |
|
|
Prefix any command above with --dry-run to simulate the underlying manager calls without touching the system: the safe way to watch what mpm would do before trusting it.
Operations¶
Operation |
Supported |
Notes |
|---|---|---|
|
✓ |
|
|
||
|
||
|
✓ |
exact and extended search backfilled by |
|
✓ |
|
|
✓ |
|
|
||
|
✓ |
|
|
||
|
||
|
Selecting and configuring pearl¶
Deselect pearl for a single run with --no-pearl, or persist the choice in your configuration:
[mpm]
pearl = false
The arguments and environment variables listed in the box atop this page are forced on every pearl call, so runs stay quiet, non-interactive and reproducible: the defaults you would set in CI anyway.
Keep it enabled but tune how mpm drives it with a per-manager override:
[mpm.managers.pearl]
timeout = 900
mpm config-template pearl prints every overridable attribute as a ready-to-paste block.
Recipes¶
A few jobs you would otherwise script around pearl, one mpm command each:
Snapshot and clone a machine:
mpm --pearl dump pearl.toml, thenmpm restore pearl.tomlon the next one.Export a compliance SBOM:
mpm --pearl sbom(CycloneDX by default,--spdxfor SPDX).
Privilege escalation¶
mpm runs this manager as the current user and never prepends sudo by default. Flip the policy for its privileged operations with --sudo or the per-manager sudo override.
None of its operations needs root.
See privilege escalation for the full policy.
Cooldown¶
State of Pearl’s release-age gating, from the cooldown support table:
Status: ❌ None (a package is a git checkout, carrying no version or date)
A cooldown only pays off where a compromised release can be withdrawn while the clock runs, and can only be emulated where the registry dates its releases. From the retraction table:
Registry: Pearl package repositories
Retraction: Repository edit: a package is an entry in a repository of recipes that clone from upstream, so it is withdrawn by that repository dropping the entry
Publish date: ❌ neither the listing nor a recipe records a version, so there is nothing to date
With --cooldown set, mpm skips this manager’s install and upgrade operations rather than run them unguarded (fail-closed); --cooldown best-effort opts back in.
Version probe¶
The version is probed by running:
$ pearl --version
pearl 2.3.12
and extracted with:
r"pearl\s+(?P<version>\S+)"
Reference traces¶
Raw native outputs captured in the bundled definition: the reference mpm’s parsers were written against. If you know Pearl well and a transcript below looks wrong, or a newer release changed its output format, report it.
$ pearl list --installed-only
pearl/airline [installed]
Status/tabline for vim
$ pearl search {query}
pearl/bufexplorer
BufExplorer Plugin for Vim
pearl/dot-vim
Awesome vim dotfiles
Feed any of these through mpm and the raw output becomes one uniform table, the same shape for every manager: filter it, project columns, or export it (mpm --pearl installed --output json, or csv, toml, yaml), each package carrying a purl and a version comparable across managers.
Changelog¶
8.0.0.dev0(unreleased)Add Pearl package manager, with inventory, search, install, remove and single-package upgrade.