Solus eopkg¶
- ID
eopkg- Home page
- Version requirement
>= 3.2
- Platforms
🐧 Linux
- Operations
installed·outdated·search·install·upgrade·upgrade_all·remove·sync·cleanup- purl types
pkg:eopkg- CLI name
eopkg- Every call
eopkg --no-color <command>- Issues and PRs
- Source
Solus’ eopkg package manager, a PiSi fork.
installed and outdated parse eopkg’s fixed-width, |-delimited
status table; the column regex requires that pipe structure, so the header
and === separator rows fall through. --no-color is forced to keep
the output free of ANSI escapes.
Mutating operations pass --yes-all to auto-confirm eopkg’s prompts so
they run unattended.
What mpm adds to eopkg¶
Through mpm, eopkg gains --exact search, to narrow results to exact names.
Bigger still, mpm reaches across every manager at once: mpm installed and mpm outdated cover eopkg 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 eopkg commands, in mpm¶
You already know eopkg: each operation maps one-to-one onto mpm, in an interface shared by every manager.
To… |
With |
With |
|---|---|---|
List what’s installed |
|
|
List outdated packages |
|
|
Search for a package |
|
|
Install a package |
|
|
Upgrade one package |
|
|
Upgrade everything |
|
|
Remove a package |
|
|
Clear caches |
|
|
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 search backfilled by |
|
✓ |
|
|
✓ |
|
|
✓ |
|
|
✓ |
|
|
✓ |
|
|
✓ |
|
|
Selecting and configuring eopkg¶
Deselect eopkg for a single run with --no-eopkg, or persist the choice in your configuration:
[mpm]
eopkg = false
The arguments and environment variables listed in the box atop this page are forced on every eopkg 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.eopkg]
timeout = 900
mpm config-template eopkg prints every overridable attribute as a ready-to-paste block.
Recipes¶
A few jobs you would otherwise script around eopkg, one mpm command each:
Snapshot and clone a machine:
mpm --eopkg dump eopkg.toml, thenmpm restore eopkg.tomlon the next one.Export a compliance SBOM:
mpm --eopkg sbom(CycloneDX by default,--spdxfor SPDX).
Privilege escalation¶
System-wide manager: mpm wraps its privileged operations in sudo out of the box. Instead of letting the tool prompt mid-run, mpm primes the credential cache up-front, with a single branded password prompt at most. Turn escalation off for rootless setups with --no-sudo or the per-manager sudo override.
See privilege escalation for the full policy.
Cooldown¶
State of Solus eopkg’s release-age gating, from the cooldown support table:
Status: ❌ None
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: Distro binary archives (
pkg:deb,pkg:rpm,pkg:alpm,pkg:apk)Retraction: Index revert: removal is an archive operation and the mirror is rebuilt without the package. Debian, for one, requires filing an
RM:bug againstftp.debian.org(developers-reference)Publish date: ❌ the version string is the distro maintainer’s build, carrying no upstream publication date
With --cooldown set, mpm skips this manager’s install and upgrade operations rather than run them unguarded (fail-closed); --allow-unsupported-managers opts back in.
Version probe¶
The version is probed by running:
$ eopkg --version
eopkg 3.2.0
and extracted with:
r"eopkg\s+(?P<version>\S+)"
Reference traces¶
Raw native outputs captured in the manager source: the reference mpm’s parsers were written against. If you know Solus eopkg well and a transcript below looks wrong, or a newer release changed its output format, report it.
$ eopkg --no-color list-installed --install-info
Package Name |St| Version| Rel.| Distro| Date
=====================================================================
aalib | i| 1.4.0_5| 8| Solus|14 Oct 2024
abseil-cpp | i| 20240116.2| 10| Solus|14 Oct 2024
accountsservice | i| 23.13.9| 36| Solus|14 Oct 2024
acl | i| 2.3.2| 21| Solus|14 Oct 2024
adwaita-icon-theme | i| 46.2| 28| Solus|14 Oct 2024
adwaita-icon-theme-legacy | i| 46.2| 2| Solus|14 Oct 2024
alsa-firmware | i| 1.2.4| 7| Solus|14 Oct 2024
alsa-lib | i| 1.2.12| 38| Solus|14 Oct 2024
alsa-plugins | i| 1.2.12| 26| Solus|14 Oct 2024
alsa-utils | i| 1.2.12| 28| Solus|14 Oct 2024
aom | i| 3.10.0| 24| Solus|14 Oct 2024
appstream | i| 1.0.1| 9| Solus|14 Oct 2024
appstream-data | i| 49| 51| Solus|14 Oct 2024
appstream-glib | i| 0.8.2| 13| Solus|14 Oct 2024
argon2 | i| 20190702| 6| Solus|14 Oct 2024
at-spi2 | i| 2.52.0| 44| Solus|14 Oct 2024
atkmm | i| 2.28.4| 19| Solus|14 Oct 2024
attr | i| 2.5.2| 25| Solus|14 Oct 2024
audit | i| 4.0.2| 19| Solus|14 Oct 2024
avahi | i| 0.8| 27| Solus|14 Oct 2024
baobab | i| 46.0| 27| Solus|14 Oct 2024
$ eopkg --no-color list-upgrades --install-info
Package Name |St| Version| Rel.| Distro| Date
=====================================================================
adwaita-icon-theme | i| 46.2| 28| Solus|14 Oct 2024
appstream-data | i| 49| 51| Solus|14 Oct 2024
at-spi2 | i| 2.52.0| 44| Solus|14 Oct 2024
baobab | i| 46.0| 27| Solus|14 Oct 2024
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 --eopkg installed --output json, or csv, toml, yaml), each package carrying a purl and a version comparable across managers.