Date: Mon, 12 Dec 2011 10:19:48 -0800 From: Kevin Oberman <kob6558@gmail.com> To: Sunpoet Po-Chuan Hsieh <sunpoet@freebsd.org> Cc: ports@freebsd.org, gerald@freebsd.org Subject: Re: lang/gcc46 Message-ID: <CAN6yY1v9FTeCg%2B0A=pdsBweov7xrxqz8w%2BiGXjVYhj5c_DhnqA@mail.gmail.com> In-Reply-To: <20111212181153.GB76159@bonjour.sunpoet.net> References: <20111212173616.GA85305@DataIX.net> <CAN6yY1s=mL0xkRJU3j9%2BmALFJBnvyAD6UF1R-k0j0mfRzZFU7w@mail.gmail.com> <20111212181153.GB76159@bonjour.sunpoet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 12, 2011 at 10:11 AM, Sunpoet Po-Chuan Hsieh <sunpoet@freebsd.org> wrote: > On Mon, Dec 12, 2011 at 10:03:14AM -0800, Kevin Oberman wrote: >> On Mon, Dec 12, 2011 at 9:36 AM, Jason Hellenthal <jhell@dataix.net> wro= te: >> > >> > Hi Gerald, >> > >> > As a request once again similiar to one I have made in the past... Wou= ld 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 versi= on 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 da= y after it was bumped to the next snapshot version & by the time both of th= ose 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= files or excluding by whatever means neccesary as weekly updates seem comp= letely 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 = weekly 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? > > We have lang/gcc already. This port is created for perferred gcc releases > (4.6.2 currently). What we're waiting for is a bsd.gcc.mk update to allow > users build ports with lang/gcc instead of lang/gcc46. Ahh. I see the issue. I have not looked at bsd.gcc.mk, but it does not seem like this should be too difficult. Just a matter of the right person having the time. Would ports specifying gcc46 need to be touched? --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1v9FTeCg%2B0A=pdsBweov7xrxqz8w%2BiGXjVYhj5c_DhnqA>