Digest and Manifest

In the tree, every package has a Manifest file. This file lives in the same directory as the ebuilds for the package. The Manifest file contains digests (currently MD5, RMD160 and SHA256) and file size data for every file in the directory and any subdirectories. This is used to verify integrity. The Manifest may also be digitally signed.

To generate the Manifest, use ebuild foo.ebuild manifest. When committing, the Manifest file must be regenerated to handle any CVS keyword expansion changes — repoman will do this automatically.