# libxo mit Homebrew, apk, dnf, MacPorts, Nix installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für libxo in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:libxo ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install libxo ``` Evidenz: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install libxo ``` Evidenz: MacPorts ports tree: devel/libxo/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - apk (92%): ```sh sudo apk add libxo ``` Evidenz: Alpine Linux edge package indexes: libxo from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz - dnf (92%): ```sh sudo dnf install libxo ``` Evidenz: Fedora Rawhide package metadata: libxo from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst - Nix (92%): ```sh nix profile install nixpkgs#libxo ``` Evidenz: nixpkgs package indexes: pkgs/by-name/li/libxo/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Paketfakten - **Paketschlüssel:** brew:libxo - **Paketmanager:** Homebrew - **Version:** 1.7.5 - **Quellzusammenfassung:** Allows an application to generate text, XML, JSON, and HTML output - **Homepage:** - **Repository:** - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - libxo-config (Alias) - xo (Alias) - xohtml (Alias) - xolint (Alias) - xopo (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 1.7.5 ## Projektgeschichte und Nutzung libxo is a C library from Juniper for emitting traditional text, XML, JSON, and HTML from one set of output calls. It is best known in package culture through FreeBSD's structured-output work. ### Projektgeschichte The project README explains the central idea: applications call xo_emit with field descriptors, and the selected output style is chosen at runtime. GitHub tag metadata places the 0.1.0 tag at a commit dated 2014-07-30. The FreeBSD manual page records Phil Shafer as author and says the library was added in FreeBSD 11.0. That adoption moved libxo from a standalone library into the base-system conversation about machine-readable command output. ### Adoptionsgeschichte FreeBSD's adoption gave libxo a practical audience: base utilities could keep human-readable output while adding JSON, XML, or HTML modes for scripts and automation. The package is also available outside FreeBSD for projects that want the same structured-output model. ### Wie es verwendet wird Users generally encounter libxo through commands that accept a libxo output mode or through the xo utility family. Developers use the library when they want one formatting path to serve terminal text and structured data consumers. ### Warum Paket-Nerds sich dafür interessieren libxo matters because it is a concrete answer to the long-running Unix problem of parsing human text with fragile awk and sed pipelines. It represents the package-manager-adjacent push toward structured CLI output without abandoning traditional command output. ### Zeitleiste - 2014: The 0.1.0 GitHub tag points to a commit dated 2014-07-30. - 2014: The FreeBSD Ports manual page date for libxo(3) is 2014-12-08. - 2016: FreeBSD 11.0 included libxo according to the FreeBSD manual page. - 2020s: libxo remains packaged for Homebrew, FreeBSD ports, and multiple Unix-like distributions. ### Related projects - FreeBSD base utilities are the most visible related ecosystem. jq and other JSON-processing tools are common downstream companions when libxo-enabled commands emit JSON. ### Quellen - - - - - ## Sicherheitshinweise library-like package without higher-risk signals. - **Geiger-Risiko:** grün / niedrig - library-like package without higher-risk signals ## Andere Paketmanager-Einträge - Nix - libxo: normalized package name match | nixpkgs package indexes: pkgs/by-name/li/libxo/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - apk - libxo - 1.7.5-r0: normalized package name match | Alpine Linux edge package indexes: libxo from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Library for Generating Text, XML, JSON, and HTML Output | http://juniper.github.io/libxo/libxo-manual.html - apk - libxo-dev - 1.7.5-r0: normalized package name match | Alpine Linux edge package indexes: libxo-dev from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Library for Generating Text, XML, JSON, and HTML Output (development files) | http://juniper.github.io/libxo/libxo-manual.html - apk - libxo-doc - 1.7.5-r0: normalized package name match | Alpine Linux edge package indexes: libxo-doc from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Library for Generating Text, XML, JSON, and HTML Output (documentation) | http://juniper.github.io/libxo/libxo-manual.html - dnf - libxo - 1.7.5-4.fc45: normalized package name match | Fedora Rawhide package metadata: libxo from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | A Library for Generating Text, XML, JSON, and HTML Output | https://github.com/Juniper/libxo - dnf - libxo-devel - 1.7.5-4.fc45: normalized package name match | Fedora Rawhide package metadata: libxo-devel from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | Development files for libxo | https://github.com/Juniper/libxo - MacPorts - libxo: normalized package name match | MacPorts ports tree: devel/libxo/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/libxo.yml](https://github.com/mxcl/pkgdb/blob/main/combined/libxo.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph