On 2025-05-07, Andrea Pappacoda wrote: > On Wed May 7, 2025 at 1:42 PM CEST, Ian Jackson wrote: >> B. Set S_D_E to the sdate but use the bdate for file mtimes in >> the .deb. We would need a separate solution for arch-specific >> archives containing mtimes (and IDK how we would even detect >> them - and detecting them seems like it might be important to >> avoid the bugs described in requirement 3). Transition plan may >> be complicated. Also how would the build obtain the *two* dates? > > I'm not really proposing any solution here, as I don't have the > experience to do so. Still, to answer your question about obtaining the > two dates, what about introducing a new variable BUILD_DATE_EPOCH which > is normally set to the same value of SOURCE_DATE_EPOCH except for > binNMUs? Build tools would then do the "right thing" (whatever it is).
There is a lot to unpack in that "whatever" ... How many compilers, toolchains or other tools would now have to support yet another environment variable? What does having another variable actually accomplish that cannot be accomplished by a single variable? live well, vagrant
signature.asc
Description: PGP signature
