From owner-freebsd-ports@FreeBSD.ORG Thu Feb 16 16:36:47 2012 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 655411065677; Thu, 16 Feb 2012 16:36:47 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0B9B38FC0C; Thu, 16 Feb 2012 16:36:46 +0000 (UTC) Received: by vcmm1 with SMTP id m1so2363743vcm.13 for ; Thu, 16 Feb 2012 08:36:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=rCNcTL47nKYIlp3+8LNC+nyAoxq4eyk4I+k30fyxDpw=; b=eNFE3b5h4C/zAiRuwFmQ5RkJdxzmsXggPVJhDdQxJC0a4sVT1tapjAms7SyJyXmOCq hVYhPBD+DfjytoDkl1yIi94xiADWiFgbnWTyookV10SqK6eMvgKGFbPDyd5u4Eh/ay5M 0uN5VCFfV9fuiuP4+6EYJsNxRuWRV5dlz4v0k= MIME-Version: 1.0 Received: by 10.52.178.40 with SMTP id cv8mr1277788vdc.82.1329410206144; Thu, 16 Feb 2012 08:36:46 -0800 (PST) Received: by 10.220.210.69 with HTTP; Thu, 16 Feb 2012 08:36:46 -0800 (PST) Date: Thu, 16 Feb 2012 16:36:46 +0000 Message-ID: From: "b. f." To: freebsd-ports@FreeBSD.org, Volodymyr Kostyrko , gerald@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: lang/gcc rumdependencies? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2012 16:36:47 -0000 >The main question is why this port (and everythin else with >USE_GCC=4.6+) depend on lang/gcc46 and not lang/gcc. Most port users >dislike building latest gcc snapshot on a weekly basis. Indeed. But (as discussed before on this list), they don't have to, if they find this to be a problem: they can remove lang/gcc46 and replace it with lang/gcc. >Maybe it would be good to move current lang/gcc46 to lang/gcc46-devel >and rename lang/gcc to lang/gcc46? No, because in time lang/gcc will become a stable release of 4.7.x, and so on ... A switch to lang/gcc is planned, as previously mentioned on this list. For the timing of the changes, you will have to ask Gerald -- he is probably waiting for the next stable release of gcc 4.6, which will contain some bugfixes that the current version of lang/gcc does not have, before making the switch. So far, stable releases have been made every 3-4 months on that branch, and the last one was at the end of October. b.