cvs commit: ports MOVED
pav at FreeBSD.org
Sat Sep 3 16:22:20 PDT 2005
Ade Lovett píše v so 03. 09. 2005 v 16:09 -0700:
> 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?
I don't consider this "a sweeping change".
> Bison 2.0 is absolutely not backwards compatible with 1.75 (see all
> the fun and games with 1.875 as an example).
That's new information for me.
> 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.
Let's see how much will actually break. If it gets bad, it will have to
be backed out, of course.
Still, the MOVED commit is strange.
Pav Lucistnik <pav at oook.cz>
<pav at FreeBSD.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/cvs-all/attachments/20050904/03694e99/attachment.bin
More information about the cvs-all