From owner-svn-ports-all@freebsd.org Sat May 21 16:38:32 2016 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EACC5B45817; Sat, 21 May 2016 16:38:32 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id DDBB8172A; Sat, 21 May 2016 16:38:32 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id DC3B51DB4; Sat, 21 May 2016 16:38:32 +0000 (UTC) Date: Sat, 21 May 2016 16:38:32 +0000 From: Alexey Dokuchaev To: Baptiste Daroussin Cc: marino@freebsd.org, Ed Maste , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r415078 - in head: . Mk Message-ID: <20160521163832.GB97771@FreeBSD.org> References: <20160513182837.GF49383@ivaldir.etoilebsd.net> <20160513201919.GA48945@FreeBSD.org> <20160519122306.GA24015@FreeBSD.org> <20160521112728.GA624@FreeBSD.org> <364d3d9f-63ff-18c8-c730-a11c57dc0673@marino.st> <20160521114358.GC624@FreeBSD.org> <20160521122522.GJ21899@ivaldir.etoilebsd.net> <70938d6b-0fab-91b9-28b0-9dd05302a503@marino.st> <20160521124148.GK21899@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160521124148.GK21899@ivaldir.etoilebsd.net> User-Agent: Mutt/1.6.0 (2016-04-01) X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 May 2016 16:38:33 -0000 On Sat, May 21, 2016 at 02:41:48PM +0200, Baptiste Daroussin wrote: > All needs it, I have provided links in previous mails that explain > reproducible builds and in particular the issue with timestamps[.] I don't think we're denying the fact that you need a suitable source of timestamps to work with. > A quick hint: this timestamp will be used as a timestamp for file inside > each packages, (but not only) in order to be sure that the tar files > itself is the has the same checksum if packaging the same files rebuilt > laters. > > The timestamps are more tricky that they looks like because of how things > like Makefile.pl, bytecodes for python, emacs etc works and are regenerated. I presume that answers John's question (which ports need it -- all do). > I really don't care about the location of the information, I care about > the fact that it is updated often enough so it does not break building > and not too often so we can benefit from reproducible build. And I somewhat do care about the location. Putting it in distinfo is not just ugly, but wrong. If you manage to convince me that it really cannot be reliably obtained from either VCS or properly exported tree then please find a better place for it. ./danfe