Several tools are available to make your life easier when working on reproducible builds.
diffoscope will try to get to the bottom of what makes files or directories different. It will recursively unpack archives of many kinds and transform various binary formats into more human-readable forms for comparison. It can compare two tarballs, ISO images, or PDFs just as easily. See an example HTML and text output.
If you wish to just experiment with diffoscope
without installing a large number of run-time dependencies, you can use the
try.diffoscope.org service directly from your
web browser. A lightweight lient is also available as the
Problems with unstable order of inputs or other variations introduced by filesystems can sometimes be hard to track down. disorderfs is an overlay FUSE filesystem that deliberately introduces non-determinism into filesystem metadata. For example, it can randomize the order in which directory entries are read.
Some tools used in build systems might introduce non-determinism in ways
difficult to fix at the source, which requires post-processing.
strip-nondeterminism knows how to normalise various file formats such as
gzipped files, ZIP archives, and Jar files. It is written in Perl with
extensibility in mind.
reprotest builds the same source code in different environments and then checks the binaries produced by the builds to see if changing the environment, without changing the source code, changed the generated binaries.
- reproducible-build-maven-plugin for the Apache Maven build tool, popular with Java projects.
- sbt-reproducible-builds plugin for the sbt build tool, popular with Scala projects.
Follow us on Twitter @ReproBuilds. Projects working on reproducible builds: Arch Linux, Baserock, Bitcoin, coreboot, Debian, ElectroBSD, F-Droid, FreeBSD, Fedora, GNU Guix, Monero, NetBSD, NixOS, OpenEmbedded, openSUSE, OpenWrt, Qubes OS, Symfony, Tails, Tor Browser, Webconverger, Yocto Project. Content licensed under CC BY-SA 4.0, style licensed under MIT. Templates and styles based on the Tor Styleguide. Logos and trademarks belong to their respective owners. Patches welcome via our Git repository (instructions) or via our mailing list.