aom

Overview

aom packages the Alliance for Open Media AV1 reference codebase. AV1 is an open video codec designed for video compression and decoding workflows where compatibility with the AV1 standard matters more than a single vendor implementation. The upstream project provides reference software for the codec, which is useful for validation, testing, integration work, and distribution packaging. (aomedia.org)

For NiceOS, this package exists so the distribution can ship a maintained build of the AV1 reference implementation in RPM form. That gives users and other packages a standard AV1 codec library and related tools without requiring them to build upstream source themselves. The exact subpackages and enabled features should always be verified in the spec file and build logs for this repository.

Purpose and typical use cases

Typical use cases for this package include:

• decoding or encoding AV1 content through software that links to libaom
• testing AV1 media pipelines against the reference implementation
• packaging and build validation in distribution or CI environments
• media tooling and integration work where standards conformance is important

Typical users include:

• distribution maintainers who update and rebuild the package
• developers integrating AV1 support into applications or dependent packages
• CI/CD maintainers who need reproducible package builds and checks
• desktop or workstation users who rely on AV1-aware applications that use the packaged library

Upstream project

Upstream is maintained by the Alliance for Open Media. The AV1 codec is described by AOMedia as an open video codec, and the organization publishes the AV1 specifications and the reference codebase. (aomedia.org)

Useful upstream reference pages:

• AV1 specification and code overview
• AOMedia open-source projects page
• AOMedia AV1 roadmap and related documentation

NiceOS maintainers should verify the upstream packaging layout against the current upstream release notes and source tree before making update decisions.

Dist-git repository contents

This dist-git repository is organized as follows:

• SPECS/ — RPM spec file(s) and packaging logic
• SOURCES/ — source metadata and manifest files used to track upstream source integrity
• METADATA/ — package metadata used by the dist-git workflow
• SBOM/ — software bill of materials artifacts, if present for this package branch

Large upstream source archives are intentionally not stored in this Git repository. Instead, the repository keeps manifest-style integrity metadata in SOURCES/, and the actual source payload is fetched or prepared by the packaging workflow.

Source storage and integrity policy

The source policy for this package is simple:

• keep large upstream archives out of Git
• track source integrity through the manifest files in SOURCES/
• update the manifest data when upstream sources change
• treat any source layout drift as a packaging change that should be reviewed, not as a routine version bump detail

Do not rely on filename changes, archive structure, or checksum assumptions without checking the packaging metadata in this branch.

NiceOS maintenance notes

Before updating this package, NiceOS maintainers should check:

• whether upstream changed the reference codebase layout or build system
• whether any spec file patches still apply cleanly
• whether the source manifest files in SOURCES/ need regeneration or replacement
• whether SBOM/ or other metadata needs to be refreshed after the update
• whether build options, subpackages, or file lists changed upstream
• whether the update affects dependent packages that link to or consume libaom
• whether the new source tree introduces packaging or licensing review items that were not present before

Practical risks to consider:

• upstream build behavior may change even when the public API appears similar
• documentation or example files may move, which can affect %files lists
• patch carry may need to be reduced or dropped if upstream absorbed the change
• reproducibility or test expectations may change across upstream releases

If any of these points are unclear, NiceOS maintainers should verify them against the current upstream source and the branch packaging rules before committing the update.

Build and verification checklist

For RPM maintenance, a reasonable checklist is:

• inspect the spec file for required package metadata and build flags
• verify the SOURCES/ manifest matches the intended upstream source payload
• confirm all patches still apply, or remove obsolete ones
• run the package build in a clean mock or equivalent build root
• review build logs for new warnings, failed tests, or unexpected disabled features
• check that installed file lists match the spec file %files sections
• verify shared library packaging, SONAME handling, and dependency generation
• run any available package tests or upstream self-tests that are appropriate for the branch
• confirm that the resulting RPMs contain only expected artifacts
• review SBOM/ and metadata files if the branch policy requires them to be updated

References

• Alliance for Open Media AV1 video codec
• Alliance for Open Media open source projects
• Alliance for Open Media specifications overview

Russian documentation

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

Dist-git repository notes

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