Per Jessen wrote:
Cristian Morales Vega wrote:
You want two builds from the same source to generate the same binary. This allows the user to verify the binary hasn't been corrupted/compromised. Also, the openSUE Build service rebuilds the package everytime a dependency changes, but after the build there is a script that checks if there is any important difference between the new build and the old one. If the two build are equal the new package is discarded, so the user doesn't needs to redownload a new package that is exactly equal to the one he already has. But __TIMESTAMP__, __DATE__ and __TIME__ macros make every build different since they add the build time to the binary. Usually you substitute the macro with the timestamp from the .changes file (using sed) to avoid the problem.
Thanks for the explanation, that was just what I needed. And look what the spec file has:
%build touch -r ./ver.c ./ver.c.stamp sed -i -e s@__DATE__@__TIMESTAMP__@ ./ver.c touch -r ./ver.c.stamp ./ver.c
However, the changelog actually says: ------------------------------------------------------------------- Mon Aug 30 22:49:25 UTC 2010 - cristian.rodriguez@opensuse.org - use __TIMESTAMP__ instead of __DATE__ to make build-compare happy. So what's the story? -- Per Jessen, Zürich (12.1°C) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org