From owner-svn-ports-head@freebsd.org Sat May 21 19:35:12 2016 Return-Path: Delivered-To: svn-ports-head@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 2234AB44FC6 for ; Sat, 21 May 2016 19:35:12 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC66A1E13 for ; Sat, 21 May 2016 19:35:11 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 313320f9-1f8b-11e6-9de8-1b78d5a2543b X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Sat, 21 May 2016 19:35:36 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u4LJZ8I0061420; Sat, 21 May 2016 13:35:08 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1463859308.1180.383.camel@freebsd.org> Subject: Re: svn commit: r415078 - in head: . Mk From: Ian Lepore To: Alexey Dokuchaev Cc: Baptiste Daroussin , marino@freebsd.org, Ed Maste , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Date: Sat, 21 May 2016 13:35:08 -0600 In-Reply-To: <20160521182211.GA96389@FreeBSD.org> References: <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> <20160521163832.GB97771@FreeBSD.org> <1463850648.1180.374.camel@freebsd.org> <20160521182211.GA96389@FreeBSD.org> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 May 2016 19:35:12 -0000 On Sat, 2016-05-21 at 18:22 +0000, Alexey Dokuchaev wrote: > On Sat, May 21, 2016 at 11:10:48AM -0600, Ian Lepore wrote: > > This is just crazy-talk. In what way is an update timestamp NOT > > "info" > > about the distribution files? The file isn't named distchecksum or > > In a way I've outlined earlier: distinfo is a set of per-distfile > values > of certain functions. TIMESTAMP is not, it's not a function of any > of > the distfiles and it is not obvious exactly how it is related to > those > distfiles. I've explained it earlier today, you should've replied to > *that* email [1] if you object. > > > dist_sha256_only, or dist_only_what_alexey_likes_to_see. It is > > metadata, it has always been metadata, and now that there is new > > metadata necessary to achieve new functionality, the one and only > > place > > that makes sense for it to be is the existing distinfo metadata > > file. > > The difference between SIZE(), SHA256(), and TIMESTAMP is that the > first > two are required to be there for reference, something to compare > against. > TIMESTAMP is just some frozen timestamp, and could be obtained > elsewhere > without breaking the whole idea (as I see it right now). Polluting > data > with not-being-a-reference metadata is just wrong from engineering > point. > > > Saying that the info can be obtained from version control is more > > crazy > > -talk. Do we add support for every version control system that > > ever > > existed to support every user of ports other there? > > Well, first, we do officially use SVN. Second, for a versioned tree, > getting correct timestamp is just a few lines for another popular > VCS, > as we speak of versioned tree. Third, I doubt that *every* ports > user > would want to know or care for reproducible builds; most just want to > change some options and "make install clean". > > > The people most interested in the new reproducible build > > functionality > > are the ones most likely to be using some local version control > > system > > which is not svn or git (we use both cvs and mercurial for various > > generations of our ports trees at $work). > > Yet when I asked why it can't be fetched from the VCS, I was told > that > we care about unversioned tarballs, and that's the problem. > > > Instead of demanding that the people actually doing useful new work > > justify this tiny insignificant detail of their implementation > > because > > it offends your view of how things should be, perhaps you could > > provide > > some argument about what harm the new value does. Something based > > on > > actual facts, not just "I think it's ugly" or "I think it's wrong." > > But I did [1]. And I'm not demanding anything, just think that > distinfo > is not the best place to put TIMESTAMP in. (And to a lesser degree, > is > that it should be possible to avoid hardcoding it anywhere, but > that's an > open debate still.) Adhering to some "harm" here looks like a straw > man > argument, sorry. > > ./danfe > > [1] http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2769892+0+current/sv > n-ports-head > So in a fairly predicable fashion, based on the way this thread has evolved, you dismiss a call for actual facts showing why an idea is bad as irrevelent and then just point again to a summary of your personal opinions and reiterate that they should rule the day. Please don't bother to CC me in any further response to this thread, it appears to be information-free, and I'm done with it. -- Ian