On Dec 23, 3:06pm, Warner Losh wrote:
} On Mon, Dec 23, 2019, 2:37 PM Kamil Rytarowski <n...@gmx.com> wrote:
} > On 23.12.2019 18:14, Greg Troxel wrote:
} > > Warner Losh <i...@bsdimp.com> writes:
} > >
} > >> Just a quick note: when FreeBSD when from 9 to 10, we had to play 'hunt
} > the
} > >> wumpus' for all the autoconfig scripts that suddenly thought they were
} > >> configuring for FreeBSD 1.0.
} > >>
} > >> If you can arrange it, it might make sense to do a pkgsrc run on an
} > >> experimental system that has the version as 10.0 rather than 9.9.xx
} > before
} > >> committing to a schedule given the experience of your sister BSD
} > project.
} > >
} > > Thanks, that's a really good point.
} >
} > This issue is well known. Once we will branch -10 we will test it in
} > HEAD and -10 concurrently.
} >
} > On the other hand, clang10 broke only a single piece of software that I
} > build (nodejs).
}
} FreeBSD 10 broke dozens of config scripts that all derived from a common
} ancestor back in the 90s... though 1.0 FreeBSD needed special treatment for
} things like a.out and such and the scripts used 1* to match. It would be
I was going to say that we could just skip 10 and go direct to
11, but 1* would catch 11 as well. So much for the shortcut.
} easy enough to grep for that pattern in gnu software to see if it will trip
} you up. NetBSDs release version history may be such this isn't an issue,
} but it broke a heck of a lot than I'd expected at the time...
}
}-- End of excerpt from Warner Losh
