From owner-freebsd-ports@freebsd.org Sat Nov 26 07:48:07 2016 Return-Path: Delivered-To: freebsd-ports@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 4E376C56CAF; Sat, 26 Nov 2016 07:48:07 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2FFF4A0; Sat, 26 Nov 2016 07:48:06 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from anthias (vie-188-118-240-138.dsl.sil.at [188.118.240.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 84E183F532; Sat, 26 Nov 2016 02:48:04 -0500 (EST) Date: Sat, 26 Nov 2016 08:47:59 +0100 (CET) From: Gerald Pfeifer To: Mark Millard cc: Dimitry Andric , svn-ports-head@freebsd.org, FreeBSD Ports Subject: Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?] In-Reply-To: <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> Message-ID: References: <86C72DB2-B9ED-4512-A88C-BD1D9A23806F@dsl-only.net> <9D54F0CC-F38C-4CCE-BC33-25C1457BD44B@FreeBSD.org> <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Nov 2016 07:48:07 -0000 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