Produce identical packages for checksum comparison?
bf1783 at googlemail.com
Sun Nov 15 02:23:31 UTC 2009
>I'm also thinking of building a simple checksum database to track what actually changes
>and what my options were when I compiled it. It would allow me to better make
>regression decisions. I could also be free to delete packages and know if I recompile
>it later that it was the exact same package with the exact same options. Very simple
>script to do that. Also if say there was an option when compiling ports to produce files
>with specific time/dates it would be helpful in pinpointing which of my port branches
>a specific file came from.
The elusive "reproducible build". Many people are interested in doing
this, and it's not as easy as it seems. Even if you edited your
filesystem or archives to change the timestamps of package files, the
toolchain used to create the binary files in packages often injects
random seeds, timestamps, file paths, uid/gid information, etc. that
creates differences from one build to the next. You may have to hack
several base system utilities, and then directly compare the checksums
of binaries in archives after unpacking, or use a more intelligent
comparison. See, for instance, one Japanese developer's attempt to do
this in NetBSD in order to create better quality control for a
Your description of your system's problems sounds bad. I think you
should concentrate on fixing those first.
More information about the freebsd-questions