Installer avahi avec Homebrew, apk, dnf, MacPorts, Nix, pacman, zypper, apt

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• avahi-autoipd
• avahi-browse
• avahi-browse-domains
• avahi-daemon
• avahi-dnsconfd
• avahi-publish
• avahi-publish-address
• avahi-publish-service
• avahi-resolve
• avahi-resolve-address
• avahi-resolve-host-name
• avahi-set-host-name

Historique du projet

The upstream README names Lennart Poettering and Trent Lloyd among the authors and describes Avahi as a DNS-SD over mDNS implementation compatible with Apple Bonjour. The official site says it is primarily targeted at Linux, runs on many BSD-like systems, and is not ported to Windows.

Avahi's architecture matters because it is not only a daemon. The source tree includes client libraries, core libraries, D-Bus API documentation, compatibility layers for Howl and Bonjour-style DNS-SD APIs, Python and UI utilities, service type databases, man pages, and XML service definitions.

The modern project infrastructure moved from older hosting patterns toward GitHub. The official site notes that in December 2023 the repositories moved from the lathiat namespace to the avahi organization namespace, and that avahi.org itself moved to GitHub Pages.

Historique d'adoption

Avahi became the default service-discovery stack for many Linux distributions because it solved the practical need for `.local` hostnames, printer discovery, file-sharing discovery, and application service announcements without Apple's proprietary Bonjour implementation. The official site explicitly says it ships by default in most distributions.

Package adoption is broad and split by component: distributions package the daemon, utilities, libraries, autoipd, compatibility libraries, and development headers. The input records packages in Homebrew, Debian/Ubuntu, Fedora, Alpine, Arch, MacPorts, Nix, and zypper ecosystems, with Debian and Ubuntu exposing `avahi-autoipd` as a named package entry for this formula mapping.

Modes d'utilisation

Typical user-facing tools include `avahi-browse`, `avahi-publish`, `avahi-resolve`, `avahi-set-host-name`, `avahi-daemon`, and `avahi-autoipd`. Services can be published through D-Bus APIs or by placing XML service definitions in `/etc/avahi/services`.

Configuration centers on `avahi-daemon.conf`, installed under the package system configuration directory, commonly `/etc/avahi/avahi-daemon.conf`. The man page also documents user browse domains through `$AVAHI_BROWSE_DOMAINS` or `~/.config/avahi/browse-domains`.

Pourquoi les passionnés de paquets s'y intéressent

Avahi is one of those packages whose importance is larger than the visible command line. It touches init systems, D-Bus activation, NSS integration through nss-mdns, C libraries, desktop printer discovery, service publication, firewall behavior, and network-manager assumptions.

For maintainers, Avahi is a compatibility and integration package: it needs correct defaults, split subpackages, service files, optional UI bindings, and careful coexistence with other mDNS stacks. Its release notes regularly mention distribution-facing changes such as systemd integration, default configuration updates, API additions, and compatibility fixes for FreeBSD, Solaris, musl, and containers.

Chronologie

• 2004: Copyright range in the upstream README begins, marking the early Avahi development era.
• 2010-2012: 0.6.x bugfix releases continued distribution hardening and system integration.
• 2016: Avahi 0.6.32 released with configuration-default changes and bug fixes.
• 2017: Avahi 0.7 released with binary TXT records in XML service files and gobject context support.
• 2020: Avahi 0.8 released with D-Bus/API additions, Qt5 and libevent mainloop integration, and CVE-2017-6519 mitigation.
• 2023: Official repositories moved to the avahi GitHub organization and the website moved to GitHub Pages.

Related projects

• nss-mdns: upstream companion project for resolving `.local` hostnames through NSS.
• Apple Bonjour/Zeroconf: compatible technology referenced by the official site.
• D-Bus: primary API transport for most Avahi usage.
• systemd and Linux distribution init systems: frequent integration points in release notes.

Sources

• https://avahi.org/
• https://raw.githubusercontent.com/avahi/avahi/master/README
• https://raw.githubusercontent.com/avahi/avahi/master/docs/NEWS
• https://raw.githubusercontent.com/avahi/avahi/master/man/avahi-daemon.conf.5.xml.in
• source_facts.package-manager