Utilities for Binman manifests

Billy Barrow 4a098ccb18 Initial commit 10 ماه پیش
scripts 4a098ccb18 Initial commit 10 ماه پیش
src 4a098ccb18 Initial commit 10 ماه پیش
.gitignore 4a098ccb18 Initial commit 10 ماه پیش
MANIFEST.usm 4a098ccb18 Initial commit 10 ماه پیش
README.md 4a098ccb18 Initial commit 10 ماه پیش

README.md

Manifest Utils for Binman

  • manifest-verify FILE verifies the signature of the manifest file FILE.
  • manifest-build DIR [--name NAME] [--key KEYFILE] [--serial SERIAL] [--description DESCRIPTION] [--remote URI] [--post-exec POSTEXEC] [--output OUTDIR] [--source-finder SOURCEXEC] [--license-finder LICENSEEXEC] [--path-scheme SCHEME] builds a manifest based on the structure in DIR.
    • --name specifies the name of the manifest, defaults to the base name of DIR.
    • --key specifies a key file to sign the manifest with, otherwise one will be created.
    • --serial specifies a serial number for this manifest, defaults to 0.
    • --description specifies a description for this manifest, defaults to the name of the manifest.
    • --remote specifies a remote mirror for this manifest (may be specified more than once).
    • --post-exec specifies the post-exec program to be run after the manifest is applied.
    • --prefix specifies a prefix to be prepended to all paths in the resulting manifest, defaults to root "/".
    • --remote-bin-prefix specifies a prefix for all remote binary files, defaults to "binaries".
    • --remote-ccs-prefix specifies a prefix for all remote source packages, defaults to "sources".
    • --output specifies a directory to save the manifest, key file, and folder structure to. When this is not specified, the build is considered "in-place" and the application will create a manifest (and key file where applicable) in the current working directory, no copies of the binary files will be made.
    • --source-finder specifies a program to run on each entry in the filesystem to determine the path to the source package for that file.
    • --license-finder specifies a program to run on each entry in the filesystem to determine the path to the license for that file.
    • --path-scheme specifies the scheme for remote paths to use:
    • analogue creates an output structure that mimics the structure of the input directory. This is the default and only valid option when --output is not specified.
    • content-hash creates a flat output structure where each file is named by the SHA512 hash of its contents.
    • path-hash creates a flat output structure where each file is named by the SHA256 hash of its path name.
  • manifest-sign FILE KEYFILE re-signs a manifest using the keys stored in KEYFILE.