Date: Mon, 9 Nov 2015 15:38:01 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Adam Weinberger <adamw@adamw.org> Cc: Gerald Pfeifer <gerald@pfeifer.com>, Guido Falsi <madpilot@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r388648 - in head/net: asterisk11 asterisk13 Message-ID: <20151109153801.GA60954@FreeBSD.org> In-Reply-To: <077EDBDC-8EF1-44FA-9D17-90345C2956F5@adamw.org> References: <201506052330.t55NUBZL020965@svn.freebsd.org> <alpine.LSU.2.20.1511082001320.2548@anthias> <564044BC.5050203@FreeBSD.org> <alpine.LSU.2.20.1511091255000.2548@anthias> <077EDBDC-8EF1-44FA-9D17-90345C2956F5@adamw.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. ;-) Plus, on some platforms, even on -CURRENT, GCC 4.2.1 is *the current* base compiler. "Modern" does not suffer from this bug: 4.8, 4.9, 5.0 are all, well, pretty modern. Even PowerPC users won't consider their base GCC 4.2.1 as "modern". 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. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151109153801.GA60954>