Date: Mon, 12 Dec 2011 12:36:16 -0500 From: Jason Hellenthal <jhell@DataIX.net> To: gerald@FreeBSD.org Cc: ports@FreeBSD.org Subject: lang/gcc46 Message-ID: <20111212173616.GA85305@DataIX.net>
next in thread | raw e-mail | index | archive | help
--J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 fl= apping and rebuilding because a port depends on it. If I am correct it is u= pdated weekly. I caught the tail end of the previous update and the day aft= er it was bumped to the next snapshot version & by the time both of those w= ere 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 file= s or excluding by whatever means neccesary as weekly updates seem completel= y 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 weekl= y updates ? Thanks, --=20 ;s =3D; --J2SCkAp4GZ/dPZZf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJO5juPAAoJEJBXh4mJ2FR+Oh8H/1tngiXB3TvISKgQ1FNA82Ae Ei1Gb9SC1gTetemTjrix1R9Oea9EhaCe/8E8pnRPdVttOwedq26PUM4sDWFyFQjp ScX7RTn+2BaDDiiz9pgf5ts+nxdANbBv+jUXxZo0lxFxoiW98BeNYd7h7fnxL4Ga Hb00gUnICuewxWy5qCS4UAOxDjWDRKZ4U7NPo1iOh+zFS4htseA+kRqvIJwd3ecc SOB7FMj2i4N9Nmq+KxqRChRuX9JoipyVPMhVvZSgnDwLrR7Isa5du32NQut0ASt3 HSCq69K04UmBsl2ni8vKkwJKJEpQyKqg2fE3a81DFrywHJqYaP3IYF6j51DOuGw= =jalI -----END PGP SIGNATURE----- --J2SCkAp4GZ/dPZZf--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111212173616.GA85305>