On Thu, Dec 12, 2002 at 10:45:25AM +1100, Luke Mewburn wrote:

=>   | or is the recommended way to update an existing -current to
=>   | "build.sh" to some DESTDIR and then pax the contents of that DESTDIR
=>   | over your existing / after it's finished successfully?
=> 
=> Currently, the easiest method for that situation is to build into
=> $DESTDIR, and then run
=> 	cd /usr/src/distrib/sets
=> 	nbmake-$MACHINE maketars
=> and then extract the tar files in $RELEASEDIR/binary/sets into /
=> (except etc.tgz, unless you want to overwrite your local config :)

Thanks for the info!  As someone who recently hosed his native compiler
during a recent "build.sh" upgrade (only to be rescued by re-installing
the "comp" set from a recent snapshot), I much appreciate anything that
will mitigate catastrophic build failure/complications. :-)

Just one quick question, though: is the above sequence of commands you
give equivalent to "build.sh -R /some/destdir"?  Or, is building a
release something different?  (I got the impression that building a
release involved building a distribution ["build.sh -d"] and then
converting that into installable tarballs.)

Cheers,

Paul.

e-mail: paul@gromit.dlib.vt.edu

"Without music to decorate it, time is just a bunch of boring production
 deadlines or dates by which bills must be paid."
        --- Frank Vincent Zappa