From owner-svn-ports-head@FreeBSD.ORG Fri Dec 6 11:27:01 2013 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0F84A6CA; Fri, 6 Dec 2013 11:27:01 +0000 (UTC) Received: from lmtp.galacsys.net (webmail.galacsys.net [IPv6:2001:1b78:0:1:d918:51d7:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id C7E051368; Fri, 6 Dec 2013 11:27:00 +0000 (UTC) Received: from martymac.org (webmail.galacsys.net [217.24.81.215]) by lmtp.galacsys.net (Postfix) with ESMTP id 69B821FA5D47; Fri, 6 Dec 2013 12:26:59 +0100 (CET) From: "Ganael LAPLANCHE" To: Alexey Dokuchaev , Ganael LAPLANCHE Subject: Re: svn commit: r335728 - head/benchmarks/bonnie++ X-Openwebmail-Date: Fri, 6 Dec 2013 13:26:59 +0200 Message-Id: <20131206104108.M59808@FreeBSD.org> In-Reply-To: <20131206102210.GA78375@FreeBSD.org> References: <201312060950.rB69opsI095759@svn.freebsd.org> <20131206095801.GA72543@FreeBSD.org> <20131206095855.GB72543@FreeBSD.org> <20131206100547.M75091@FreeBSD.org> <20131206102210.GA78375@FreeBSD.org> X-Mailer: Open WebMail 2.01 20030425 X-OriginatingIP: 88.163.147.236 (ganael.laplanche@martymac.org) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Fri, 06 Dec 2013 11:27:01 -0000 X-List-Received-Date: Fri, 06 Dec 2013 11:27:01 -0000 On Fri, 6 Dec 2013 10:22:10 +0000, Alexey Dokuchaev wrote > Since these bit-stirring changes inside the binary are hardly > user-visible, yes, I think it was an overkill. But it does > not hurt, of course. I just do not like to rebuild things for > no real reason. I mean, if user is happy with installed > package (built with gcc46), why force him/her to rebuilt it > just for the sake of using different compiler? Of course I fully understand we want to avoid re-building software when it is not needed, but the fact that a same package version can embed different binaries bothers me, that's why I decided to bump the PORTREVISION. My original thought was more about being able to identify that this compiler has been used to produce that specific package version. But as any version of Gcc can be used in this case, this was probably meanless. Cheers, -- Ganael LAPLANCHE http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac , http://www.FreeBSD.org