Skip to content

Sphinx build: Stabilize PDF metadata across builds#5447

Open
WeiqunZhang wants to merge 2 commits into
AMReX-Codes:developmentfrom
WeiqunZhang:build_docs
Open

Sphinx build: Stabilize PDF metadata across builds#5447
WeiqunZhang wants to merge 2 commits into
AMReX-Codes:developmentfrom
WeiqunZhang:build_docs

Conversation

@WeiqunZhang
Copy link
Copy Markdown
Member

Setting SOURCE_DATE_EPOCH before make latexpdf so pdfTeX produces byte-identical amrex.pdf when the documentation source hasn't changed, avoiding a new ~7 MB blob in git on every deploy. The fixed epoch (441763200 = 1984-01-01 UTC) pins CreationDate, ModDate, and /ID.

Setting SOURCE_DATE_EPOCH before make latexpdf so pdfTeX produces
byte-identical amrex.pdf when the documentation source hasn't changed,
avoiding a new ~7 MB blob in git on every deploy.  The fixed epoch
(441763200 = 1984-01-01 UTC) pins CreationDate, ModDate, and /ID.
@WeiqunZhang WeiqunZhang requested review from asalmgren and atmyers May 16, 2026 05:00
@WeiqunZhang WeiqunZhang enabled auto-merge (squash) May 16, 2026 05:00
@WeiqunZhang
Copy link
Copy Markdown
Member Author

Note that in AMReX-Codes.github.io's git repo, there are more than 5000 versions of amrex.pdf, mainly because of the metadata difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant