meta_package_manager.managers.antidote module¶

meta_package_manager.managers.antidote.antidote_source_path()[source]¶

Locate the antidote.zsh file every invocation sources.

Falls back to the documented clone location when none of the candidates exists, so the built command stays well-formed and simply fails to source, which is what makes the version probe double as Antidote’s presence check.

Return type:

Path

class meta_package_manager.managers.antidote.Antidote[source]¶

Bases: PackageManager

Antidote is a Zsh plugin manager, successor to antibody.

Antidote clones each bundle from GitHub or any other forge into $ANTIDOTE_HOME, and records it in the user’s .zsh_plugins.txt file. Packages are identified by the user/repo slug Antidote both reports and accepts, which is the id mpm keys them on.

Caution

antidote is a shell function, not a standalone binary: the antidote script shipped in the repository carries a Zsh shebang but is not executable, and Homebrew installs it as package data under share/antidote rather than linking it into bin. Every invocation is therefore wrapped in zsh -c 'source <antidote.zsh> && antidote <args>'. Zsh is the manager’s CLI, and Antidote’s own presence is established by the version probe: a host with Zsh but no Antidote fails to source and reports no version, which leaves the manager unavailable.

Note

No search: Antidote resolves bundles straight from forge URLs and indexes no registry to search.

Note

No upgrade_one: antidote update takes no bundle argument, only the --self and --bundles scope flags, so a single bundle cannot be targeted. mpm auto-skips the operation and upgrade --all still works.

Documentation: antidote.sh.

Initialize cli_errors list.

homepage_url: str | None = 'https://antidote.sh'¶

Home page of the project, only used in documentation for reference.

Slug of the brand mark standing for this manager in the documentation.

Names an SVG vendored under docs/assets/managers/, whose provenance and license are recorded in docs/assets/managers/logos.yaml. Inlined at the top of the manager’s page by meta_package_manager._docs; a manager leaving it unset keeps the page’s default package glyph.

Several managers legitimately share one slug, either because they wrap the same upstream (brew and cask) or because the tool has no mark of its own and its ecosystem’s stands in (apt under Debian’s swirl, cargo under Rust’s gear). Documentation-only, like homepage_url: no CLI output reads it.

platforms: frozenset[Platform] | Group | Platform | Iterable[Platform | Group] = frozenset({Platform(id='almalinux', name='AlmaLinux'), Platform(id='alpine', name='Alpine Linux'), Platform(id='altlinux', name='ALT Linux'), Platform(id='amzn', name='Amazon Linux'), Platform(id='android', name='Android'), Platform(id='arch', name='Arch Linux'), Platform(id='buildroot', name='Buildroot'), Platform(id='cachyos', name='CachyOS'), Platform(id='centos', name='CentOS'), Platform(id='chromeos', name='ChromeOS'), Platform(id='clearlinux', name='Clear Linux OS'), Platform(id='cloudlinux', name='CloudLinux OS'), Platform(id='debian', name='Debian'), Platform(id='endeavouros', name='EndeavourOS'), Platform(id='exherbo', name='Exherbo Linux'), Platform(id='fedora', name='Fedora'), Platform(id='generic_linux', name='Generic Linux'), Platform(id='gentoo', name='Gentoo Linux'), Platform(id='guix', name='Guix System'), Platform(id='ibm_powerkvm', name='IBM PowerKVM'), Platform(id='kali', name='Kali Linux'), Platform(id='kvmibm', name='KVM for IBM z Systems'), Platform(id='linuxmint', name='Linux Mint'), Platform(id='macos', name='macOS'), Platform(id='mageia', name='Mageia'), Platform(id='mandriva', name='Mandriva Linux'), Platform(id='manjaro', name='Manjaro Linux'), Platform(id='nixos', name='NixOS'), Platform(id='nobara', name='Nobara'), Platform(id='opensuse', name='openSUSE'), Platform(id='openwrt', name='OpenWrt'), Platform(id='oracle', name='Oracle Linux'), Platform(id='parallels', name='Parallels'), Platform(id='pidora', name='Pidora'), Platform(id='pikaos', name='PikaOS'), Platform(id='raspbian', name='Raspbian'), Platform(id='rhel', name='RedHat Enterprise Linux'), Platform(id='rocky', name='Rocky Linux'), Platform(id='scientific', name='Scientific Linux'), Platform(id='slackware', name='Slackware'), Platform(id='sles', name='SUSE Linux Enterprise Server'), Platform(id='slitaz', name='SliTaz GNU/Linux'), Platform(id='sourcemage', name='Source Mage GNU/Linux'), Platform(id='tuxedo', name='Tuxedo OS'), Platform(id='ubuntu', name='Ubuntu'), Platform(id='ultramarine', name='Ultramarine'), Platform(id='void', name='Void Linux'), Platform(id='wsl1', name='Windows Subsystem for Linux v1'), Platform(id='wsl2', name='Windows Subsystem for Linux v2'), Platform(id='xenserver', name='XenServer')})¶

List of platforms supported by the manager.

Allows for a mishmash of platforms and groups of platforms. Will be normalized into a frozenset of Platform instances at instantiation.

requirement: str | None = '>=2.2.0'¶

First release whose list --jsonl and update --dry-run are both sound.

Both landed in 2.0.0, but each carried a defect this implementation depends on being fixed: 2.1.1 repaired list --jsonl emitting invalid JSON whenever a value held a quote, backslash or control character, and 2.2.0 stopped update --dry-run deepening shallow clones, a permanent side effect that made a dry run something other than a query. 2.2.0 also fixed antidote update reporting success when a worker had failed, which is the exit code mpm reads to mark the operation.

cli_names: tuple[str, ...] = ('zsh',)¶

Zsh is the binary mpm actually executes.

Antidote is a shell function defined by an antidote.zsh file that is sourced, never executed, so it cannot serve as the manager’s CLI: mpm requires an executable. Keying the manager on Zsh instead makes the version probe the presence check, since sourcing an absent antidote.zsh yields no version and leaves the manager unavailable.

extra_env: ClassVar = {'NO_COLOR': '1', 'SHELL_SESSIONS_DISABLE': '1'}¶

Antidote gives NO_COLOR precedence over every other color signal, so the parsers see clean text. SHELL_SESSIONS_DISABLE keeps macOS’ Zsh session bookkeeping from writing a session file on every query.

version_regexes: tuple[str, ...] = ('antidote version (?P<version>\\S+)',)¶

Antidote appends the short commit of its own checkout to the release it reports.

$ zsh -c 'source ~/.antidote/antidote.zsh && antidote --version'
antidote version 2.3.0 (9bb69ab)
id: str = 'antidote'¶

Package manager’s ID.

Derived by defaults from the lower-cased class name in which underscores _ are replaced by dashes -.

This ID must be unique among all package manager definitions and lower-case, as they’re used as feature flags for the mpm CLI.

name: str = 'Antidote'¶

Return package manager’s common name.

Default value is based on class name.

virtual: bool = False¶

Should we expose the package manager to the user?

Virtual package manager are just skeleton classes used to factorize code among managers of the same family.

build_cli(*args, **kwargs)[source]¶

Wrap all CLI invocations in the Zsh shell Antidote needs.

The version probe is guarded by a readability test that exits successfully when antidote.zsh is absent. Zsh is the default shell on macOS and near ubiquitous elsewhere, so an unguarded probe would turn every host that merely has Zsh into a manager reporting errors. An antidote.zsh that is present but broken still fails loudly.

Note

The **kwargs accepted by the base class (auto_pre_args, sudo, etc.) are accepted but ignored because every invocation goes through the zsh -c wrapper and Antidote never requires elevated privileges.

Return type:

tuple[str, ...]

property installed: Iterator[Package]¶

Fetch installed packages.

Antidote emits one JSON object per line rather than a single array, so the listing is decoded line by line. The sha reported for a bundle is the Git commit its clone is checked out at, which is the only revision Antidote records: a bundle is tracked by branch unless the user pins it with a pin: annotation.

$ zsh -c 'source ~/.antidote/antidote.zsh && antidote list --jsonl'
{"url":"https://github.com/rupa/z","repo":"rupa/z","path":"/home/kev/.cache/antidote/github.com/rupa/z","sha":"d37a763a6a30e1b32766fecc3b8ffd6127f8a0fd"}
{"url":"https://github.com/zsh-users/zsh-completions","repo":"zsh-users/zsh-completions","path":"/home/kev/.cache/antidote/github.com/zsh-users/zsh-completions","sha":"729a2408fb129bcda7e8a21ae7bf349fe295b634"}
property outdated: Iterator[Package]¶

Fetch outdated packages.

--dry-run fetches each bundle’s remote and reports what an update would move, without touching a single working tree. Both revisions are the short commits Antidote prints, so an outdated bundle reads as a commit-to-commit move rather than a version bump: bundles are tracked by branch, and Antidote records no version of its own.

$ zsh -c 'source ~/.antidote/antidote.zsh && antidote update --dry-run'
Checking for bundle updates (dry run)...
antidote: checking for updates: rupa/z
antidote: checking for updates: zsh-users/zsh-completions
Waiting for bundle updates to complete...

Bundle rupa/z update check complete.
antidote: update available: rupa/z b82ac78 -> d37a763
d37a763 Escape calls for sed and awk in case someone aliased them (#264)
703bb54 avoid issues when ``date`` has been aliased
6ba0722 avoid issues when ``env`` has been aliased

Dry run complete. No changes were made.

antidote: skipping self-update (dry run)
install(package_id, version=None)[source]¶

Install one package.

install both clones the bundle and appends it to the user’s .zsh_plugins.txt, so a package installed through mpm is loaded by the next shell instead of sitting on disk unreferenced.

$ antidote install rupa/z
Adding bundle to '/home/kev/.zsh_plugins.txt':
rupa/z
Return type:

str

upgrade_all_cli()[source]¶

Generates the CLI to upgrade all packages.

Note

Scoped to --bundles so the update stays a package operation. A bare antidote update also updates Antidote itself, which is the manager rather than a package, and which would mean a Git pull inside a Homebrew keg on a host that installed it that way.

$ antidote update --bundles
Return type:

tuple[str, ...]

remove(package_id)[source]¶

Remove one package.

purge is the exact counterpart of Antidote.install(): it drops the clone and comments the bundle out of the user’s .zsh_plugins.txt, so the next shell no longer loads it.

$ antidote purge rupa/z
Removed 'rupa/z'.
Bundle 'rupa/z' was commented out in '/home/kev/.zsh_plugins.txt'.
Return type:

str