EVR: 1.5.3-1 Lock-SHA256: 034a017b2051576860a6e4877a7387b11f69e382f2c8fc02fa08fac74e3bcf92 Branch: niceos-5.2 |
||
|---|---|---|
| METADATA | ||
| SBOM | ||
| SOURCES | ||
| SPECS | ||
| .gitignore | ||
| OWNERS | ||
| README.md | ||
| README_RU.md | ||
dav1d
Overview
dav1d is an AV1 decoder project from VideoLAN. Its upstream project describes it as a small, portable, fast AV1 decoder. In a Linux distribution, this package provides the decoder component needed by software that needs to read or process AV1 video streams. (code.videolan.org)
Purpose and typical use cases
Typical use cases include:
- playback or processing of AV1 video in media applications
- media pipelines that need a standalone AV1 decoder library or executable component
- distribution packaging work where the decoder is delivered as a system package rather than bundled by individual applications
The package is most relevant to maintainers of multimedia stacks, developers integrating AV1 support, and users or administrators who need AV1 decoding on the system. Security or codec-specific behavior should be verified by NiceOS maintainers against the current upstream release and packaging state before relying on it.
Upstream project
Upstream is maintained by VideoLAN. The project page identifies dav1d as an AV1 decoder and links it with the AV1 codec and fast decoding work. The upstream repository also provides compilation guidance, which may be useful when checking build options or platform support during package updates. (code.videolan.org)
Dist-git repository contents
This dist-git repository is organized into the usual RPM packaging directories:
SPECS/— RPM spec files and packaging logicSOURCES/— source metadata and manifest files used by the build systemMETADATA/— repository metadata used by the packaging workflowSBOM/— software bill of materials data when present
The repository is intended to contain packaging metadata, not the full upstream source tree.
Source storage and integrity policy
Large upstream source archives are intentionally not stored in this Git repository. Instead, source integrity is tracked through manifest files in SOURCES/. When updating the package, maintainers should verify that the expected upstream source is still represented by the manifests and that the packaging metadata matches the files being built.
Do not assume that a spec update is safe just because the repository content changed in a small way. Source replacement, tarball regeneration, or manifest refresh may be required.
NiceOS maintenance notes
Before updating this package, NiceOS maintainers should check:
- whether upstream changed build requirements, supported compilers, or platform assumptions
- whether the spec file needs changes for new build options, enabled architectures, or packaging policy updates
- whether any files in
SOURCES/need regeneration or refresh because upstream content changed - whether
SBOM/or other metadata needs to be updated to match the new source set - whether the license files and packaging metadata still match the upstream repository layout and licensing terms
Risks to consider:
- build failures caused by upstream build-system changes
- accidental mismatch between spec expectations and the actual upstream source contents
- packaging regressions if a new upstream release changes default behavior or optional components
- arch-specific issues that only appear in the distribution build environment
If any of these points are unclear, NiceOS maintainers should verify them against upstream before publishing the update.
Build and verification checklist
A practical RPM maintainer checklist for this package:
- Refresh
SOURCES/manifests if the upstream source reference changed. - Review the spec file for new or removed build requirements.
- Confirm that the build root can resolve all declared dependencies.
- Build the package in a clean environment.
- Inspect build logs for compiler warnings or unexpected feature toggles.
- Run the package's available test or smoke-test steps if they are enabled in the spec.
- Verify that the installed files and package provides/requirements look correct.
- Check license files and metadata against upstream.
- Review
SBOM/and repository metadata if your workflow expects them to stay in sync. - Test any downstream consumers that depend on AV1 decoding if the change is substantial.
References
Russian documentation
Dist-git repository notes
- Package repository:
rpms/dav1d - NiceOS branch:
niceos-5.2 - This README is intentionally stable and does not include EVR, source archive checksums or lock hashes.