Date: Sat, 3 Sep 2005 16:09:33 -0700 From: Ade Lovett <ade@FreeBSD.org> To: pav@FreeBSD.org Cc: cvs-ports@FreeBSD.org, ports-committers@FreeBSD.org, cvs-all@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: cvs commit: ports MOVED Message-ID: <A20B8F13-EDA6-4431-B1FB-00CADEC6AEB2@FreeBSD.org> In-Reply-To: <1125784854.60066.16.camel@ikaros.oook.cz> References: <200509021957.j82JvKMW075037@repoman.freebsd.org> <1125784204.60066.13.camel@ikaros.oook.cz> <20050903215856.GA51280@xor.obsecurity.org> <1125784854.60066.16.camel@ikaros.oook.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sep 03, 2005, at 15:00 , Pav Lucistnik wrote: > I did actually built all ports that uses bison before committing this > update, and I found single failure, which I handled using bison175 > port. Which bit of "no sweeping changes before 6.0-RELEASE" was unclear? Bison 2.0 is absolutely not backwards compatible with 1.75 (see all the fun and games with 1.875 as an example). Just because ports *build* with the new bison does not mean that they actually work correctly. If anything, devel/bison should have been left as-is, and a devel/bison20 brought in (along the lines of the existing bison1875 port). > More to say, that MOVED line does not prevent portupgrade from > updating > to 2.0, just tested it. I'd love to know the reasoning behind Ade's > commit. Because I was expecting you to do the right thing, and bring in devel/ bison20, and not blindly upgrade a port with a large number of consumers to an incompatible release, in the middle of a ports slush. The MOVED entry was a subtle hint towards the way things should have been done. Obviously, it was *too* subtle. Right now, the best thing you could do would be to revert the update of devel/bison back to 1.75 then *after* 6.0-RELEASE happens, bring up a devel/bison20, kill off devel/bison (at which point the MOVED entry will work), and manage the upgrade in a more appropriate manner. - -aDe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDGi0tpXS8U0IvffwRAo8JAJ0dq5wKTP5wQWu89ff+10faduqKYgCfSEI/ uGiL+jAC1b+AM7JNuqqJNUE= =RVGj -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A20B8F13-EDA6-4431-B1FB-00CADEC6AEB2>