Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PATCH: please consider making doxygen output byte for byte identical between individual runs by default (Origin: bugzilla #745439) #5753

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity enhancement in component general for ---
Reported in version 1.8.8-GIT on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2015-03-02 10:31:57 +0000, marivalenm@gmail.com wrote:

Created attachment 298265
Change the default of HTML_TIMESTAMP from YES to NO

"With free software, anyone can inspect the source code for malicious flaws.[...] The idea of �deterministic� or �reproducible� builds is to empower anyone to verify that no flaws have been introduced during the build process by reproducing byte-for-byte identical binary packages from a given source" https://wiki.debian.org/ReproducibleBuilds/About

In Debian there are about 300 source packages that are not byte for byte reproducible between different rebuilds because doxygen includes a timestamp. https://reproducible.debian.net/issues/timestamps_in_documentation_generated_by_doxygen_issue.html

We observed that 70% of these source packages do not explicitly set the HTML_TIMESTAMP variable. Thus, if doxygen would change the default of this variable to not generate timestamps, most of these packages will immediately become reproducible.

Please also consider implementing this for this other patch of mine: https://bugzilla.gnome.org/show_bug.cgi?id=744938

The attached patch changes the default of HTML_TIMESTAMP from YES to NO

On 2015-03-05 20:54:45 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next GIT update.

On 2015-06-27 19:02:02 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.10. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.