meta_package_manager.managers.roswell module¶

class meta_package_manager.managers.roswell.Roswell[source]¶

Bases: PackageManager

Roswell, a Common Lisp implementation installer and launcher.

Important

A roswell package is a Lisp implementation, not a Lisp library. ros install``accepts both an implementation and a Quicklisp system, but``ros list installed answers for implementations alone: a system installed with ros install cl-ppcre never appears there. The two verbs disagree on their object, and this wrap resolves it the way RustUp resolves the same question, by narrowing to what the listing can enumerate.

Caution

remove is deliberately absent. ros delete <impl> reports success on every channel that matters, exiting 0 with sbcl-bin was deleted successfully.``and an empty``<stderr>, and leaves roswell unusable: its own runtime core was built against the implementation just deleted, so every later subcommand answers <impl>/<version> does not exist.stop.. Recovery means deleting ~/.roswell and running ros setup again, ros config set being just as broken as the rest. mpm will not drive a removal that reports success and breaks the tool.

Caution

upgrade is absent for the same reason remove is, one level up: ros update``resolves its argument through``asdf:find-system, so it upgrades Quicklisp systems, never the implementations installed() reports. Mapping it here would upgrade something other than what mpm just listed.

Documentation: Roswell wiki.

Initialize cli_errors list.

name: str = 'Roswell'¶

Return package manager’s common name.

Default value is based on class name.

homepage_url: str | None = 'https://roswell.github.io/'¶

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.

keywords: tuple[str, ...] = ('common lisp', 'quicklisp')¶

Well-known names for this manager that its id does not already carry.

Merged into the PyPI keywords of pyproject.toml by docs_update.update_keywords(), alongside every manager ID and the globally curated KEYWORDS_EXTRAS. Declare an alias here rather than in that tuple whenever it names this manager: an alias living beside the class it describes cannot outlive it, where a central entry silently rots once the manager is renamed or dropped.

Reserve KEYWORDS_EXTRAS for terms belonging to no manager in particular, like cyclonedx or package manager. Documentation-only: no CLI output reads it.

platforms: frozenset[Platform] | Group | Platform | Iterable[Platform | Group] = frozenset({Platform(id='aix', name='IBM AIX'), 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='crux', name='CRUX'), Platform(id='cygwin', name='Cygwin'), Platform(id='debian', name='Debian'), Platform(id='dragonfly_bsd', name='DragonFly BSD'), Platform(id='endeavouros', name='EndeavourOS'), Platform(id='exherbo', name='Exherbo Linux'), Platform(id='fedora', name='Fedora'), Platform(id='freebsd', name='FreeBSD'), Platform(id='generic_linux', name='Generic Linux'), Platform(id='gentoo', name='Gentoo Linux'), Platform(id='guix', name='Guix System'), Platform(id='haiku', name='Haiku'), Platform(id='hurd', name='GNU/Hurd'), Platform(id='ibm_powerkvm', name='IBM PowerKVM'), Platform(id='illumos', name='illumos'), 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='midnightbsd', name='MidnightBSD'), Platform(id='netbsd', name='NetBSD'), Platform(id='nixos', name='NixOS'), Platform(id='nobara', name='Nobara'), Platform(id='nutyx', name='NuTyX'), Platform(id='openbsd', name='OpenBSD'), Platform(id='opensuse', name='openSUSE'), Platform(id='openwrt', name='OpenWrt'), Platform(id='oracle', name='Oracle Linux'), Platform(id='os400', name='IBM i'), 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='solaris', name='Solaris'), Platform(id='solus', name='Solus'), Platform(id='sourcemage', name='Source Mage GNU/Linux'), Platform(id='sunos', name='SunOS'), Platform(id='tuxedo', name='Tuxedo OS'), Platform(id='ubuntu', name='Ubuntu'), Platform(id='ultramarine', name='Ultramarine'), Platform(id='void', name='Void Linux'), Platform(id='windows', name='Windows'), 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 = '>=22.12.14.113'¶

The oldest release whose listing this parser was checked against.

lisp/list-installed.lisp is byte-identical from there through the current 26.02.116, the *error-output* header included, so the shape below is not a property of the release that happened to be driven.

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

List of CLI names the package manager is known as.

This list of recognized CLI names is ordered by priority. That way we can influence the search of the right binary.

..hint::

This was helpful in the case of the Python transition from 2.x to 3.x, where multiple versions of the same executable were named python or python3.

By default, this property’s value is derived from the manager’s ID (see the MetaPackageManager.__init__ method above).

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

The trailing (NO-GIT-REVISION) is left out of the capture: it names the build, not the version, and a release tarball carries it in place of a commit.

$ ros --version
roswell 26.02.116(NO-GIT-REVISION)
property version: TokenizedString | None[source]¶

Parse the version off <stderr>, where roswell alone prints it.

Both ros --version and ros version leave <stdout> empty and write to <stderr>, measured at 0 and 35 bytes respectively. The inherited probe reads the return value of run_cli(), which is <stdout>, so it would find nothing and leave the manager permanently unavailable. The streams are reached through _last_run instead, the same attribute bin and gext read for their own <stderr>-reporting operations.

id: str = 'roswell'¶

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.

property installed: Iterator[Package]¶

Fetch installed Lisp implementations.

Only the rows reach <stdout>; roswell prints its headings to <stderr>, so the payload arrives with no furniture to skip.

An implementation is listed once per installed version, so the rows are reduced to the newest version of each.

Caution

An empty listing is not proof of an empty machine. Roswell answers 0 with nothing on <stdout> and its diagnosis on <stderr> alone once it can no longer resolve the implementation it runs on, which a ros delete of the wrong version is enough to cause. must_succeed cannot catch that, keying on the exit code, so the two streams are compared instead and a silent failure is raised rather than reported as zero packages.

$ ros list installed
sbcl-bin/2.6.8
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.

install(package_id, version=None)[source]¶

Install one Lisp implementation.

A version is appended to the implementation with a slash, the same impl/version spelling installed() reports.

$ ros install sbcl-bin
$ ros install sbcl-bin/2.6.8
Return type:

str