[patch] proposeed changes for the pms document eapi 9

0001-emerge.tex-allow-external-timestamp-source-for-file-.patch (text/plain), 1.58 KB, created by Timothy Kenno Handojo on 2024-07-05 16:42:30 UTC

From 779b28562d330dd86cdd29b9626494acec6fb8f0 Mon Sep 17 00:00:00 2001
From: Timothy Kenno Handojo <[e-mail]>
Date: Fri, 5 Jul 2024 23:39:59 +0700
Subject: [PATCH] emerge.tex: allow external timestamp source for file mtime

This external timestamp would make a more deterministic mtime,
paving a way for reproducible build.

Bug: https://bugs.gentoo.org/934804
Signed-off-by: Timothy Kenno Handojo <[e-mail]>
---
 merge.tex | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/merge.tex b/merge.tex
index e51c1b8..5ab0e67 100644
--- a/merge.tex
+++ b/merge.tex
@@ -83,6 +83,12 @@ that for any two preserved files $a$, $b$ in that filesystem the
 relation $\mbox{mtime}(a) \leq \mbox{mtime}(b)$ still holds, if it
 held under the original image directory.
 
+Starting with EAPI 9, the mtime of respective packages' ebuild files
+can be used as a source of time for the final files, with which each package
+would have the mtime of its file content set to its ebuild file's mtime.
+For example, when building foo v1.2 and bar v3.5, the package contents of
+bar would have the mtime of foo-1.2.ebuild, and bar-3.5.ebuild for bar.
+
 In other EAPIs, the behaviour with respect to file modification times
 is undefined.
 
@@ -95,7 +101,8 @@ is undefined.
       \multicolumn{1}{c}{\textbf{mtimes preserved?}} \\
       \midrule
       0, 1, 2             & Undefined \\
-      3, 4, 5, 6, 7, 8, 9 & Yes       \\
+      3, 4, 5, 6, 7, 8    & Yes       \\
+      9                   & Yes, or from ebuild \\
       \bottomrule
     \end{tabular}
 \end{centertable}
-- 
2.44.2