omnipackage.org valid

OmniPackage documentation

Reference, guides, and CLI docs for OmniPackage — build signed RPM and DEB packages for multiple Linux distros from one YAML config.

For agents: OmniPackage docs: CLI reference and guides for building signed RPM and DEB packages for multiple Linux distros from one YAML config, with S3 publishing.

rpm packagesdeb packageslinux packaginggpg signingcli

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T11:57:06.040Z. Cached copy · Source on omnipackage.org

# OmniPackage documentation

> Reference, guides, and CLI docs for OmniPackage — build signed RPM and DEB packages for multiple Linux distros from one YAML config.

OmniPackage is a CLI that drives standard Linux packaging tools (rpmbuild, debuild, createrepo_c, dpkg-scanpackages, gpg, podman/docker) from a single YAML config, so one project repo can ship signed RPM and DEB packages to many distros from a single `release` command.

## Getting started

- [Home](https://docs.omnipackage.org/index.md): Documentation home — what OmniPackage is, links into the rest of the site.
- [Getting started](https://docs.omnipackage.org/getting_started/index.md): Install the CLI and build the bundled C example end-to-end.

## Guides

- [How it works](https://docs.omnipackage.org/guides/how_it_works/index.md): Architecture overview — how the CLI orchestrates rpmbuild/debuild/createrepo_c/gpg/podman.
- [Signing packages](https://docs.omnipackage.org/guides/signing/index.md): GPG key generation, storing the key as a secret, and signing RPM/DEB packages and repository metadata.
- [Publishing to S3](https://docs.omnipackage.org/guides/s3_repository/index.md): Publishing the built repository to S3-compatible storage (AWS S3, Cloudflare R2, MinIO).
- [Publishing to a local directory](https://docs.omnipackage.org/guides/localfs_repository/index.md): Publishing the built repository to a local directory with the localfs provider — for testing, same-machine installs, and self-hosting. S3 is not required.
- [Install page](https://docs.omnipackage.org/guides/install_page/index.md): Generated install files — install.html, install.sh, install.json, badge.svg — and custom install page templates.
- [Templates](https://docs.omnipackage.org/guides/templates/index.md): Liquid templating for the RPM .spec and DEB control files — per-distro values and shared snippets.
- [Build recipes](https://docs.omnipackage.org/guides/build_recipes/index.md): Build patterns for tricky projects — CMake/Qt, Electron, pacman — plus the Qt6 dependency map, patching staged source, and package verification.
- [CI/CD integration](https://docs.omnipackage.org/guides/cicd/index.md): Running OmniPackage in CI/CD — GitHub Actions matrix, caching, and the recommended release flow.
- [Best practices](https://docs.omnipackage.org/guides/best_practices/index.md): Recommended patterns for production package pipelines.
- [Troubleshooting](https://docs.omnipackage.org/guides/troubleshooting/index.md): Diagnosing OmniPackage build failures — missing deps, unpackaged files, link/OOM errors, per-distro package-name lookup.

## Configuration

- [Overview](https://docs.omnipackage.org/configuration/index.md): config.yml top-level keys and overall structure.
- [builds](https://docs.omnipackage.org/configuration/builds/index.md): builds — per-distro build target definitions.
- [version_extractors](https://docs.omnipackage.org/configuration/version_extractors/index.md): version_extractors — strategies for stamping the pack
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=omnipackage.org · GET /v1/domain/omnipackage.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for omnipackage.org:
1. POST https://agentwebmap.com/v1/sites/omnipackage.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://omnipackage.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/omnipackage.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/omnipackage.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.