From owner-freebsd-ports@FreeBSD.ORG Mon Dec 12 18:03:16 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01DF0106564A for ; Mon, 12 Dec 2011 18:03:16 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 924408FC0C for ; Mon, 12 Dec 2011 18:03:15 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so11836207wgb.31 for ; Mon, 12 Dec 2011 10:03:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=2RiMKbh3sLg5fsNENPoOK5N3W/yf/OqgFcmCVqN6cI8=; b=cQUsOXe15ltSC2HsxBBWp521moJ2oNo/bGy9em+1u0GMnoVIVQIWqKZlKe/qCI93WI c95aSk+297MStwE1nUUd7l96ZCcd6b+OJX2c+qqMxfEiVHmO1MhTQ6VzcsZrs7L+ck+D 19FckN5yA9aB3b+EI3dDFntzeV+USWvsuOz5E= MIME-Version: 1.0 Received: by 10.216.4.162 with SMTP id 34mr2529812wej.14.1323712994390; Mon, 12 Dec 2011 10:03:14 -0800 (PST) Received: by 10.223.92.152 with HTTP; Mon, 12 Dec 2011 10:03:14 -0800 (PST) In-Reply-To: <20111212173616.GA85305@DataIX.net> References: <20111212173616.GA85305@DataIX.net> Date: Mon, 12 Dec 2011 10:03:14 -0800 Message-ID: From: Kevin Oberman To: Jason Hellenthal Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: ports@freebsd.org, gerald@freebsd.org Subject: Re: lang/gcc46 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2011 18:03:16 -0000 On Mon, Dec 12, 2011 at 9:36 AM, Jason Hellenthal wrote: > > Hi Gerald, > > As a request once again similiar to one I have made in the past... Would = it be possible yet to slow down the update process for the gcc46 port ? > > This is turning out to be quite the pain in the U-Know-What with version = flapping and rebuilding because a port depends on it. If I am correct it is= updated weekly. I caught the tail end of the previous update and the day a= fter it was bumped to the next snapshot version & by the time both of those= were finished the port had once again been bumped to _1. > > Is there anything that could be done to stabalize this ... ? > > At this point I am left for the manual intervention of using +IGNOREME fi= les or excluding by whatever means neccesary as weekly updates seem complet= ely unneccesary now that alot of ports are shifting to depend on gcc46. > > Can a gcc46-devel port be branched for those that absolutely need the wee= kly updates ? +1 gcc46 is used by so many ports that I am continually re-building it and on slow machines, this takes a while. How about a gcc46-devel port that gets the regular updates and let gcc46 stay stable when there are not major fixes? - R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com