[MacPorts] #59672: Set SOURCE_DATE_EPOCH
MacPorts
noreply at macports.org
Sat May 11 16:23:30 UTC 2024
#59672: Set SOURCE_DATE_EPOCH
--------------------------+----------------------
Reporter: ryandesign | Owner: (none)
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: base | Version:
Resolution: | Keywords: haspatch
Port: |
--------------------------+----------------------
Comment (by jmroot):
Replying to [comment:9 ryandesign]:
> Replying to [comment:6 tenzap]:
> > May I suggest to add the revision number of the port (the value in the
Portfile) to the timestamp in SOURCE_DATE_EPOCH? This would be like adding
a few seconds to it and permit to represent in SOURCE_DATE_EPOCH that the
Portfile changed. This is sort of analogous to the way debian does it
(Debian uses the timestamp of the debian/changelog file).
>
> I don't know if that's a good idea. I don't see anything recommending
doing that in the documentation link I posted at the top. I am not
familiar with what Debian does or why it does it.
Debian increments the value only in the case of a Binary Non-Maintainer
Upload. We don't have the problem that that solves for them. The
equivalent of a Portfile change normally results in a new entry in
`debian/changelog` which has a new timestamp.
--
Ticket URL: <https://trac.macports.org/ticket/59672#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list