On Thu, Jan 16, 2020 at 03:14:46PM -0700, Alan Feuerbacher via blfs-support wrote: > > You're right about the permissions problem: I've been building and testing > as root during this entire build. I changed the owner of all appropriate > files in my LFS system from root:root to lfs:wheel, since lfs is > unprivileged, and then built the offending packages again. All ok now. > > This brings up something I'm a bit confused about: Several years ago one of > you LFS staff guys suggested that I build everything as root, since that was > his own practice, even though not recommended by LFS staff. But it's now > clear to me that the staff recommendations really ought to be followed, > which I'm doing from now on. > Possibly me: for my own normal builds I mostly stay as root. There are a few packages which *have to* be built as a normal user. But then I only run tests for very few packages on my own builds.
My view is that the perceived safety benefits of using sudo will not buy me very much support when I'm in "deep build" mode ;-) OTOH, backups often halp. For kernels, even at the end of an LFS build, I _do_ usually build as a normal user (lfs at the end of LFS, my normal user for later kernel upgrades). And for when I'm editing, I follow the book: build as a user, run tests as a user where appropriate, DESTDIR or similar to see what gets installed. ĸen -- The politics of wizardry were either very simple, and resolved by someone ceasing to breathe, or as complex as one ball of yarn in a room with three bright-eyed little kittens. - Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
