Date: Fri, 27 Jul 2012 02:57:47 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Peter Jeremy <peter@rulingia.com> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Gerald Pfeifer <gerald@freebsd.org>, ports-committers@freebsd.org Subject: Re: svn commit: r301534 - head/chinese/ibus-pinyin Message-ID: <20120727025747.GA51135@FreeBSD.org> In-Reply-To: <20120726220254.GA25547@server.rulingia.com> References: <201207252136.q6PLam3L002419@svn.freebsd.org> <20120726220254.GA25547@server.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 27, 2012 at 08:02:54AM +1000, Peter Jeremy wrote: > On 2012-Jul-25 21:36:48 +0000, Gerald Pfeifer <gerald@freebsd.org> wrote: > >Log: > > Replace USE_GCC=4.4+ by USE_GCC=4.6+ since GCC 4.4 is on its way out > > and GCC 4.6 has been the default for a while. > > I've seen quite a few of these commits and do not understand the purpose > of them. "USE_GCC=4.4+" means that this port needs gcc-4.4 or higher to > build/run. That has not changed and if I have gcc-4.4 already installed > then this port should continue to build and run without issues. That's exactly my situation as well. With insanely frequent GCC updates, I prefer to have built one version of GPLv3'ed gcc, which appeared to be 4.4. As long it works, I see no reason to update, esp. considering high build times. However, changes like this one make it harder as I have to manually adjust GCC requirement (essentially backing out your changes) to keep things working for me. USE_GCC=4.4+ seems more correct because it reflects the reality. Changing it to 4.6 implies that port cannot be built with 4.4 or 4.5, which is not true for most of the cases. Whether we keep gcc4.4 in the tree or not is different issue: users might have it installed long ago, and be perfectly happy with the package regardless of port's deprecated status. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120727025747.GA51135>