From owner-cvs-all@FreeBSD.ORG Mon Sep 26 00:25:32 2011 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B20B6106564A; Mon, 26 Sep 2011 00:25:32 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) by mx1.freebsd.org (Postfix) with ESMTP id 8DB4D8FC0C; Mon, 26 Sep 2011 00:25:32 +0000 (UTC) Received: from g159.suse.de (charybdis-ext.suse.de [195.135.221.2]) by ainaz.pair.com (Postfix) with ESMTPSA id CBA933F416; Sun, 25 Sep 2011 20:25:29 -0400 (EDT) Date: Mon, 26 Sep 2011 02:25:30 +0200 (CEST) From: Gerald Pfeifer To: Doug Barton In-Reply-To: <4E7FAABC.2070206@FreeBSD.org> Message-ID: References: <201109252159.p8PLxRLO047800@repoman.freebsd.org> <4E7FAABC.2070206@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: cvs-ports@FreeBSD.org, Gerald Pfeifer , cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/lang/gcc/files java-patch-hier patch-unwind-ia64.h X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: **OBSOLETE** CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2011 00:25:32 -0000 On Sun, 25 Sep 2011, Doug Barton wrote: > Given that we already have versioned gcc ports what is the value of > adding an unversioned, um, version. :) That's a fair question -- you just have been a bit too quick while I have been working on an updated pkg-plist and the commit message. :-) Basically the purpose is to establish a "preferred" version of GCC for Joe User and Jane Porter. And keep rebuilds of that one to a minimum. On the first, a step on a path towards establishing a preferred version of GCC amidst all the flavors, this is similar to the current USE_FORTRAN=yes which transparently picks a preferred version of GCC already. That used to be lang/gcc45 and has been upgraded to lang/gcc46 recently after an appropriate pointyhat run. On the second, see PR 156857 for a concrete user request and some thinking around that. This port of GCC, lang/gcc, will always correspond to one of the ports that are tracking snapshots and conflict with that one, lang/gcc46 for now. As a user, you have the choice to go for the release-based version which is only updated every couple of months, or track the current snapshot. Gerald PS: And some of the other lang/gcc* ports really need to die. I have spent quite some time towards paving that road for lang/gcc34 where lang/objc and some annoying ports around g77 (cad/sceptre and science/elmer-matc, science/elmerpost) are the major hold offs, and lang/gcc44 which we carry exclusively for the sake of cad/salome.