Manage system packages

Search, preview, install, update, remove, and clean system packages with the limits of each native backend.

Release v0.1.224 · Reviewed

On this page

Check the backend first#

Install the build for your operating system and run package transactions as your regular user. OMG requests elevation when its native backend needs it.

PlatformPackage sourceLimit to keep in mind
Arch LinuxOfficial repositories and AURAUR packages build from reviewed recipes
Debian and UbuntuNative APTPackage cache cleanup is not implemented
FedoraDNF and RPMNo AUR builds
Apple Silicon macOSHomebrewNo AUR builds
Native WindowsNoneUse a supported WSL distribution

The debian-pure build feature supports index and test work. It refuses live Debian or Ubuntu package mutations. See installation for the release and backend matrix.

Find a package and its source#

omg search ripgrep

The first three matches in the recorded Arch Linux session on OMG v0.1.224 were:

  ripgrep 15.2.0-1  ℹ Official
  ripgrep-all 0.10.10-3  ℹ Official
  ripgrep-all-git 0.10.10.462.g0f10fb9-1  ⚠ AUR

Press Enter on a result to inspect its details or Esc to return to the prompt. Package versions and ordering follow your current package index.

To see more metadata, restrict the search to official packages, or inspect a package by name:

omg search ripgrep --detailed --limit 30
omg search ripgrep --no-aur
omg info ripgrep

Search defaults to 15 results. On Arch, it includes AUR entries unless you pass --no-aur. --detailed adds source metadata where available. A name match or security grade does not certify the package's behavior.

Use --json only with commands whose output contract you have checked in the CLI reference.

To inspect an installed package's relationships and disk use:

omg why ripgrep
omg why ripgrep --reverse
omg size --limit 10
omg size --tree ripgrep
omg blame ripgrep

Available details depend on the backend and recorded history. --reverse asks what depends on the package.

Preview and install#

omg install --dry-run ripgrep
omg install ripgrep

The preview describes the requested operation without applying the package transaction. It can still read package metadata and contact sources. The real command can install dependencies and change the system package database.

Name several packages in one invocation when you want one operation. Bare omg install requires an attended picker and fails without a terminal. It does not install a project's application dependencies.

--yes skips ordinary confirmation. --review forces PKGBUILD review for AUR builds. Normal AUR review is already enabled by the released default aur.review_pkgbuild setting. Separate AUR approvals and policy checks are not blanket-disabled by --yes.

For a local package archive, explicitly permit file input:

omg install --allow-local-file ./package.pkg.tar.zst

Use an archive format supported by your backend and review its origin first. See security for policy and signature limits.

Check and apply updates#

omg outdated
omg update --check
omg update --dry-run
omg update

The normal update workflow can update system packages and managed runtimes. On Arch, it also handles installed AUR packages. A successful check does not prove that a later build, download, or transaction will succeed.

Use these options only for the workflow they describe:

  • --check lists updates without installing them.
  • --dry-run previews the transaction.
  • --yes skips ordinary confirmation.
  • --review forces review for each AUR build.
  • --no-sync uses cached package metadata.
  • --aur-only skips the official database sync and system upgrade on Arch.
  • --fast combines sync and upgrade without a preview.
  • --turbo skips sync and uses cached data with the optimized Arch path.

--aur-only conflicts with both --fast and --turbo. These performance modes do not promise equivalent support on every backend. Prefer the normal update path while diagnosing a failure.

omg sync refreshes package metadata without installing updates. Refreshing metadata can change a later preview.

Remove and clean deliberately#

omg remove --dry-run ripgrep
omg remove ripgrep

--recursive also removes unused dependencies on Arch. Other backends do not promise that behavior. Add --yes only after reviewing the package set.

Bare omg clean lists cleanup actions. Preview a chosen action before applying it:

omg clean --orphans --dry-run
omg clean --cache --dry-run
omg clean --aur --dry-run

--all combines orphan, cache, and AUR cleanup. --yes skips ordinary confirmation. The APT backend rejects --cache, --aur, and --all. Fedora supports orphan and downloaded package cache cleanup, with no AUR cleanup.

On Arch, cache cleanup keeps one recent package version by default. Warnings about versions mentioned in history do not preserve those artifacts. Cleanup can therefore remove files needed for a later rollback.

Check results and retain recovery evidence#

omg explicit
omg explicit --count
omg ec
omg tc
omg oc
omg uc
omg history --limit 5

The four short counters report explicit, total, orphan, and available-update counts. A cached count can lag a transaction. Use package metadata and the transaction result to confirm the actual change.

Command errors return a nonzero status. A dry run or a successful status report does not certify the safety of a future transaction. Security scans report findings without failing by default; CI must request omg audit scan --fail-on-findings for a finding gate.

History covers supported OMG transactions, rather than every action through the native package manager. Rollback depends on the backend and older package availability. It does not restore all machine state.

If a transaction fails, keep its output and inspect omg doctor before deleting caches or retrying with different privileges. Use the native package tool to investigate backend failures. Read troubleshooting for bounded diagnostics, configuration for released AUR settings, and updates for updating OMG itself.