avahi

Overview

Avahi provides local network service discovery through mDNS/DNS-SD. In practical terms, it helps systems find and advertise services such as printers, file shares, and other network resources on a local link without manual host-by-host configuration. Avahi is primarily intended for Linux systems and is widely used by desktop and server installations that need zero-configuration service discovery. (avahi.org)

For a Linux distribution, the package typically exists to supply the daemon, client libraries, tools, and integration points needed by applications that rely on multicast DNS and service discovery. Exact packaging splits can vary, so NiceOS maintainers should verify the installed subpackages and enabled integration points in this repository before making assumptions about runtime behavior. (avahi.org)

Purpose and typical use cases

Typical use cases include:

• discovering printers and other shared services on a local network
• advertising a service on the local link so other hosts can find it
• enabling applications to resolve .local hostnames and service records where the platform and configuration support it
• providing service-discovery plumbing for desktop environments, lab networks, and small infrastructure deployments

Typical users include:

• desktop users who need network discovery on a local LAN
• administrators who manage printer, file, or service discovery on managed networks
• developers integrating application discovery or local-service advertisement
• CI/CD or image-build maintainers who need reproducible package updates and verification in RPM workflows
• security engineers reviewing service exposure on a local network and package integration choices

Upstream project

The upstream project is Avahi, whose official site describes it as a system for service discovery on a local network using the mDNS/DNS-SD protocol suite. The upstream GitHub organization hosts the main project repository and the website source. (avahi.org)

Useful upstream references:

• project website and overview
• upstream source repository
• Doxygen API documentation for native interfaces

If NiceOS maintainers need to rely on a detail that is not obvious from those sources, verify it against the upstream repository or release notes before updating the package. (avahi.org)

Dist-git repository contents

This dist-git repository is organized as a standard RPM packaging tree:

• SPECS/ — RPM spec files and packaging logic
• SOURCES/ — source manifest files and other source-control metadata used by the build
• METADATA/ — repository metadata used by the packaging workflow
• SBOM/ — software bill of materials material when maintained for this package

The large upstream source archive is intentionally not stored in Git. Instead, the repository tracks source integrity through manifest files in SOURCES/, which allow the build system to verify the expected source set without checking in bulky upstream archives. NiceOS maintainers should keep that policy intact unless the packaging workflow changes. (github.com)

Source storage and integrity policy

The intent of this repository is to keep versioned packaging metadata in Git, not the full upstream release archive.

What to expect:

• Git contains the spec file, repository metadata, and source manifest information.
• Upstream source archives are fetched or provided separately by the build workflow.
• SOURCES/ records the expected source inputs so the build can validate what it uses.

What not to expect:

• large tarballs committed directly into the repository
• mutable build output
• version-specific checksum values in this README

If the packaging layout changes, maintainers should update the manifests and any related packaging metadata together, then verify that the build still consumes the intended upstream source set. (github.com)

NiceOS maintenance notes

Before updating this package, NiceOS maintainers should check the following:

• confirm the upstream release or commit to be packaged
• review upstream release notes, NEWS files, and changelogs for behavior changes
• check whether any spec file patches can be dropped, refreshed, or need new adjustments
• verify whether bundled generated files in SOURCES/ or SBOM/ need regeneration
• confirm that file ownership, subpackage layout, and service integration still match NiceOS policy
• review whether the update changes default behavior, build requirements, or runtime integration points that matter to downstream users
• consider whether the update affects local network exposure, daemon startup behavior, or desktop integration

Risks to consider:

• upstream changes in build tooling or generated files may require spec adjustments
• local network service discovery can interact with firewall, multicast, and name-resolution policy
• packaging splits may change across upstream releases, so NiceOS should verify installed artifacts rather than assume they remain stable

Build and verification checklist

For RPM maintenance, a reasonable update checklist is:

1. refresh the source manifest in SOURCES/ if the upstream source set changes
2. update the spec file for any new patches, build requirements, or file layout changes
3. verify the package still builds cleanly in a clean mock or equivalent build environment
4. inspect the resulting subpackages for expected binaries, libraries, services, and documentation
5. run the package test or smoke-test steps that are available in the build environment
6. confirm that install, upgrade, and removal paths remain sane for the packaged artifacts
7. check that any service units, D-Bus integration, or helper binaries still behave as expected
8. review the generated SBOM material, if maintained here, for consistency with the packaged contents

If any of these checks depend on local policy or downstream integration details, NiceOS maintainers should verify them explicitly before tagging the update. (avahi.org)

References

• Avahi project website
• Avahi upstream GitHub repository
• Avahi Doxygen documentation

Russian documentation

See README_RU.md for the Russian version of this document.

Dist-git repository notes

• Package repository: rpms/avahi
• NiceOS branch: niceos-5.2
• This README is intentionally stable and does not include EVR, source archive checksums or lock hashes.