Date: Fri, 19 Jan 2018 17:17:53 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Tijl Coosemans <tijl@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r459019 - in head/benchmarks: . lzbench Message-ID: <20180119171753.GA90466@FreeBSD.org> In-Reply-To: <20180115111845.0b7ec2f7@kalimero.tijl.coosemans.org> References: <201801150705.w0F75r9C001017@repo.freebsd.org> <20180115111845.0b7ec2f7@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 15, 2018 at 11:18:45AM +0100, Tijl Coosemans wrote: > On Mon, 15 Jan 2018 07:05:53 +0000 (UTC) Alexey Dokuchaev wrote: > > Because GitHub releases (tarballs) are not fetched with correct > > modification time, set TIMESTAMP to 1515146810 which corresponds to > > commit 6c4ad37 tagged as this release. > > I've seen you say this a couple of times now and I don't think it really > matters. If I remember correctly TIMESTAMP isn't really related to > distfiles. It has something to do with reproducible builds. All files > generated during build are supposed to get this timestamp or something, > so the same port built on different machines at different times results > in exactly the same package. Tijl (sorry for delayed reply), Yeah, I know about the idea behind the TIMESTAMP thingy. I not saying that having some kind of timestamp attached to a port is bad or unneeded thing, or that reproducible builds are useless, etc. I'm just not very happy with current implementation. I've tried to make my point before: https://lists.freebsd.org/pipermail/svn-ports-all/2016-May/124839.html https://lists.freebsd.org/pipermail/svn-ports-all/2016-June/125564.html ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180119171753.GA90466>