mkmanifest

mkmanifest [options] directory

-f filename
    Specify the output filename for the manifest. If not provided, it often defaults to 'manifest' or 'Manifest'.

-m algorithm
    Specify the checksum algorithm to use (e.g., md5, sha1, sha256). Defaults to md5 if not provided in many implementations.

-r
    Recursively include files in subdirectories.

directory
    The directory to scan for files to include in the manifest.

The mkmanifest command is a tool used to generate a build manifest file. This file lists all the files within a specified directory along with their checksums (typically MD5). This manifest can be used to verify the integrity of a build, ensuring that no files have been modified or corrupted since the manifest was created.

It is commonly employed in software development and deployment processes to track and validate build artifacts. The primary purpose is to provide a reliable record of the contents of a build, facilitating validation during installation or later auditing. The generated manifest typically includes the filename and associated checksum for each file in the targeted directory and its subdirectories if specified by flags. This can be useful for verifying file integrity after transfer or storage. Different implementations exist but the core functionality remains the same.

The specific options and behavior of mkmanifest can vary depending on the implementation. Some versions might have additional features or limitations. Always consult the specific version's documentation for accurate information.

The choice of checksum algorithm depends on the security requirements. MD5 is fast but considered cryptographically weak. SHA-1 is also deprecated. SHA-256 or SHA-512 are recommended for more secure environments.

md5sum(1), sha1sum(1), sha256sum(1)