Subject: Re: Updating an existing system?
To: Paul Mather <email@example.com>
From: Luke Mewburn <firstname.lastname@example.org>
Date: 12/12/2002 10:45:25
On Wed, Dec 11, 2002 at 04:40:46PM -0500, Paul Mather wrote:
| Is there anything analogous in the build.sh procedure to FreeBSD's
| make buildworld / make installworld
Not yet, but I'm working on a solution to this. (See below).
| 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
and then extract the tar files in $RELEASEDIR/binary/sets into /
(except etc.tgz, unless you want to overwrite your local config :)
I'm working on a solution to allow you to copy a build into $DESTDIR
into / (whether or not you've built using UNPRIVED), and only copying
stuff that would have been updated if you had extracted the following
base comp games man misc text
For a variety of reasons involving the circular dependencies that can
result regarding "which part of the system do you update first",
building directly into / is not the "safest" of build practices, which
is why we have /usr/src/UPDATING to (hopefully) help you manually work
around such issues when they occur. Building into $DESTDIR (generally)
avoids these issues. To be even "safer", you can build using UNPRIVED
as an ordinary user, from a read-only source tree.