Subject: Re: HEADS UP: new build.sh & top level Makefile functionality ...
To: Luke Mewburn <email@example.com>
From: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
Date: 12/30/2002 16:33:43
On Mon, Dec 30, 2002 at 23:43:32 +1100, Luke Mewburn wrote:
> | The only catch was that after the build as user all directories in DESTDIR
> | were of mode 700. My umask=022. How can I make sure they get mode=755?
> | I do the install over NFS with root=nobody, so all files must be world
> | readable.
> Since you're running build.sh with -U (UNPRIVED), you should run the
> installworld with the same option, so that the build system knows to
> Do The Right Thing with permissions from the info stored in
I will check my system for the permissions. However, my question was
about the build phase. After the build the directories in DESTDIR
are 700 and thus not readable by root over NFS.
> To make things easier, I'd just change your installation routine to:
> # yyy/bin/nbmake-`uname -m` UPDATE=1 installworld
> I.e, run "$TOOLDIR/bin/nbmake-$MACHINE" with "UPDATE=1 installworld".
> As nbmake-$MACHINE is a shell script wrapper to $TOOLDIR/bin/nbmake
> which contains the various settings from the last time you ran build.sh,
> it already has the settings for DESTDIR, TOOLDIR, UNPRIVED, (...)
> You could simplify things even more by using "-u" with build.sh; then
> you don't need "UPDATE=1" on installworld commandline.
Hmm, interesting. I did not know this. Time to update the documentation :-)