From owner-svn-ports-head@freebsd.org Mon Nov 9 15:41:49 2015 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 72FBFA29245; Mon, 9 Nov 2015 15:41:49 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [204.109.59.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "abg.ninja", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D2E7B15F1; Mon, 9 Nov 2015 15:41:48 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 31edc874 TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 9 Nov 2015 08:41:45 -0700 (MST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: svn commit: r388648 - in head/net: asterisk11 asterisk13 From: Adam Weinberger In-Reply-To: <20151109153801.GA60954@FreeBSD.org> Date: Mon, 9 Nov 2015 08:41:43 -0700 Cc: Gerald Pfeifer , Guido Falsi , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <201506052330.t55NUBZL020965@svn.freebsd.org> <564044BC.5050203@FreeBSD.org> <077EDBDC-8EF1-44FA-9D17-90345C2956F5@adamw.org> <20151109153801.GA60954@FreeBSD.org> To: Alexey Dokuchaev X-Mailer: Apple Mail (2.3096.5) X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.20 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: Mon, 09 Nov 2015 15:41:49 -0000 > On 9 Nov, 2015, at 8:38, Alexey Dokuchaev wrote: > > On Mon, Nov 09, 2015 at 08:28:58AM -0700, Adam Weinberger wrote: >> What about "Build with current GCC (from ports)"? >> With or without those parentheses. >> >> Then people know that they're about to build/install a new compiler, >> which is a large and time-consuming dependency. > > Again, I advocate for s/current/modern/. What is "current"? It can be > 4.9 for some people, 5.0 for others, and "why should I care" for everyone > else. ;-) I agree with everything you just said. > I'm still hesitating about "Build with" vs. "Use". I'm thinking of cases > when GCC bits are required, but not exactly to build things. At this point > I'm more inclined towards "Use modern GCC (from ports)" but still not 100% > confident it's the best wording. I think the difference there is pedantic, and possibly more confusing. While it is true that "build with" may not always be accurate, "use" is so generic as to convey practically nothing. My vote is for "Build with modern GCC (from ports)" # Adam -- Adam Weinberger adamw@adamw.org http://www.adamw.org