TazPkg

Note

SliTaz has published no stable ISO since 5.0 (2023) but shows active development into 2026; tazpkg remains its native package manager.

ID

tazpkg

Links

Home page · Documentation · Repository · Wikipedia

Platforms

🐧 Linux (SliTaz GNU/Linux only)

Operations

installed · search · install · upgrade · upgrade_all · remove · sync · cleanup

purl types

pkg:tazpkg/

CLI name

tazpkg

Every call

tazpkg <command> --output=raw

Forced environment

LC_ALL=C

Issues and PRs

📦 manager: tazpkg

Source

tazpkg.py

SliTaz GNU/Linux’s package manager.

The code also lives in a git clone, SliTaz-official/tazpkg.

What mpm adds to tazpkg

Through mpm, tazpkg 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 tazpkg 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 tazpkg commands, in mpm

You already know tazpkg: each operation maps one-to-one onto mpm, in an interface shared by every manager.

To…	With tazpkg	With mpm
List what’s installed	tazpkg list	mpm --tazpkg installed
Search for a package	tazpkg search nano	mpm --tazpkg search nano
Install a package	sudo tazpkg get-install nano --forced	mpm install pkg:tazpkg/nano
Upgrade one package	sudo tazpkg get-install nano --forced	mpm --tazpkg upgrade nano
Upgrade everything	sudo tazpkg up -i	mpm --tazpkg upgrade --all
Remove a package	sudo tazpkg remove nano	mpm remove pkg:tazpkg/nano
Clear caches	sudo tazpkg clean-cache	mpm --tazpkg cleanup --cache

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
installed	✅
outdated
orphans
search	✅	Exact and extended search backfilled by mpm.
install	✅
upgrade	✅
upgrade_all	✅
remove	✅
sync	✅
cleanup	✅
doctor

Configuration

• Ignore tazpkg on the mpm CLI by passing the --no-tazpkg option.

• Ignore it for every run in your configuration:

  [mpm]
  tazpkg = false
  

• Raise the timeout of all tazpkg calls:

  [mpm.overrides.tazpkg]
  timeout = 900
  

• Run mpm config-template tazpkg to print all overridable settings for your configuration file:

  [mpm.overrides.tazpkg]
  cli_names = [
      "tazpkg",
  ]
  cli_search_path = []
  dry_run = false
  ignore_auto_updates = true
  plan = false
  post_args = [
      "--output=raw",
  ]
  pre_args = []
  pre_cmds = []
  stop_on_error = false
  unmaintained = false
  version_cli_options = [
      "-F	",
      "$1==\"tazpkg\"{print $2}",
      "/var/lib/tazpkg/installed.info",
  ]
  version_regexes = [
      "^(?P<version>[\\d.]+)$",
  ]
  
  [mpm.overrides.tazpkg.extra_env]
  LC_ALL = "C"
  

The arguments and environment variables listed in the box atop this page are forced on every tazpkg call, so runs stay quiet, non-interactive and reproducible: the defaults you would set in CI anyway.

Recipes

A few jobs you would otherwise script around tazpkg, one mpm command each:

• Snapshot and clone a machine: mpm --tazpkg dump tazpkg.toml, then mpm restore tazpkg.toml on the next one.

• Export a compliance SBOM: mpm --tazpkg sbom (CycloneDX by default, --spdx for 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.

Its privileged operations are cleanup, install, remove, sync, upgrade, upgrade_all.

See privilege escalation for the full policy.

Cooldown

State of TazPkg’s release-age gating, from the cooldown support table:

Status: ❌ None (SliTaz)

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 against ftp.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); --cooldown best-effort opts back in.

Reference traces

A collection of raw native outputs captured from the manager’s own CLI and recorded in the manager source. If you know TazPkg well and a transcript below looks wrong, or a newer release changed its output format, report it.

$ tazpkg list --output=raw
List of all installed packages
================================================================================
busybox                            1.36.0            base-system
nano                               6.2               editors
================================================================================
2 packages installed.

Version check

The version is extracted from the output of awk -F $1=="tazpkg"{print $2} /var/lib/tazpkg/installed.info with:

r"^(?P<version>[\d.]+)$"

Changelog

• 7.2.0 (2026-07-09)

  • Add TazPkg (SliTaz GNU/Linux) package manager with installed, search, install, upgrade, remove, sync and cleanup support.