Section: flatpak build-update-repo (1)
flatpak-build-update-repo - Create a repository from a build directory
flatpak build-update-repo [OPTION...] LOCATION
Updates repository metadata for the repository at
LOCATION. This command generates an OSTree summary file that lists the contents of the repository. The summary is used by flatpak remote-ls and other commands to display the contents of remote repositories.
After this command,
can be used as the repository location for flatpak remote-add, either by exporting it over http, or directly with a file: url.
The following options are understood:
Show help options and exit.
Redirect this repo to a new URL.
A title for the repository, e.g. for display in a UI. The title is stored in the repository summary.
A single-line comment for the remote, e.g. for display in a UI. The comment is stored in the repository summary.
A full-paragraph description for the remote, e.g. for display in a UI. The description is stored in the repository summary.
URL for a website for the remote, e.g. for display in a UI. The url is stored in the repository summary.
URL for an icon for the remote, e.g. for display in a UI. The url is stored in the repository summary.
A default branch for the repository, mainly for use in a UI.
Import a new default GPG public key from the given file.
The globally unique identifier of the remote repository, to allow mirrors to be grouped. This must be set to a globally unique reverse DNS string if the repository is to be made publicly available. If a collection ID is already set on an existing repository, this will update it. If not specified, the existing collection ID will be left unchanged.
Deploy the collection ID (set using
--collection-id) in the static remote configuration for all clients. This is irrevocable once published in a repository. Use it to decide when to roll out a collection ID to users of an existing repository. If constructing a new repository which has a collection ID, you should typically always pass this option.
Sign the commit with this GPG key. This option can be used multiple times.
GPG Homedir to use when looking for keyrings
Generate static deltas for all references. This generates from-empty and delta static files that allow for faster download.
Limit the number of parallel jobs creating static deltas. The default is the number of cpus.
Don't generate deltas for runtime or application id matching this pattern. For instance, --static-delta-ignore-ref=*.Sources means there will not be any deltas for source refs.
Remove unreferenced objects in repo.
Only keep at most this number of old versions for any particular ref. Default is -1 which means infinite.
Print debug information during command processing.
Print OSTree debug information during command processing.