Date: Sat, 26 Nov 2016 08:47:59 +0100 (CET) From: Gerald Pfeifer <gerald@pfeifer.com> To: Mark Millard <markmi@dsl-only.net> Cc: Dimitry Andric <dim@FreeBSD.org>, svn-ports-head@freebsd.org, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?] Message-ID: <alpine.LSU.2.20.1611260832560.2407@anthias.pfeifer.com> In-Reply-To: <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> References: <86C72DB2-B9ED-4512-A88C-BD1D9A23806F@dsl-only.net> <9D54F0CC-F38C-4CCE-BC33-25C1457BD44B@FreeBSD.org> <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 25 Nov 2016, Mark Millard wrote: > I wonder if that leaves lang/gcc and lang/gcc49 as conflicting. Yes, these two ports conflict for the time being, and are properly marked as such. (And I am looking for a more elegant approach going forward, in particular when we move into GCC 5 territory where, based on input from Tijl and others, we now distinguish between lang/gcc5 and lang/gcc5-devel.) > But luckily so far I've not picked to build anything that built > lang/gcc. Or, more likely(?), if some gcc is already installed it > is used instead if lang/gcc is not installed yet. Correct. If lang/gcc49 or lang/gcc is installed, either of the two is picked up; if a newer version is installed and USE_GCC=yes or USE_GCC=X.Y+ are requested (and the installed version is newer), that one is used. Nothing to do with luck on your side, Mark. Rather, design and implementation in the Ports Collection. :-) Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LSU.2.20.1611260832560.2407>