On 02-Jun-01 matthew green wrote:
> while i do see this as extremely valuable for cross compiling, there are
> already solutions that deal with this, eg, garbled/sommerfeld's (?) mega
> cross compile script.

While I can understand some of the fears about this massive change to the
build.. I really think if we made the build run more like the crosscomp stuff,
it would actually be a win.  I have found that I can jump from something like
1.5 to -current with that, and not hit any of the nasty little chicken-egg
scenarios that we allways hit when going to current.   UPDATING is a nice
document and all.. but in reality, I think the way crosscomp solves it is far
better.

If the native build system utilized something like this, I think users trying
to do source upgrades would be much better off.  Yes, it takes longer to build
a system using something like crosscomp, and if the tree switches to a method
like that, it's going to take more time, but by building all the tools first..
we really do solve so many problems, and will reduce the thousands of emails to
-current about "lint busted, now what?".

---
Tim Rightnour <root@garbled.net>
NetBSD: Free multi-architecture OS http://www.netbsd.org/
NetBSD supported hardware database: http://mail-index.netbsd.org/cgi-bin/hw.cgi