Bryan Gardiner wrote: > On Sun, 24 Jun 2012 17:48:33 -0500 > Dale <rdalek1...@gmail.com> wrote: > > So those that allow users to run would have the same permissions as > everyone else. Now I wonder why they vary from system to system > then. It seems to me, they should be the same for everyone. Just > seems odd. > > Dale > > :-) :-) > I generally "emerge -p" as user then "emerge" as root. For ownership > of /var/log/portage/elog, I tried changing my system with portage:root > to portage:portage and vice versa on the other system. Something > during right the merge phase, right around when those elog messages > appear, resets the ownership back to what is was before I changed it > on both systems. Odd indeed. > > I thought perhaps some user flag in FEATURES would do this, but the > only difference between the two is buildpkg vs. buildsyspkg. The only > user FEATURE enabled is userfetch. Running portage-2.2.0_alpha112 on > both. > > - Bryan > > I always use the -a option. If everything looks good, I can hit the "y" key and let it go. Doing it your way, it has to calculate the thing twice. If you have a fast rig, it may not matter much tho.
I used to use the -p option but I was glad to see the -a option. I was using my old AMD 2500+ single core system back then and it saved me a LOT of time. I guess the habit stuck when I built my new rig. My new rig is AMD 3.2Ghz with 4 cores and 16Gbs of ram with portages work directory on tmpfs. HUGE difference. It is odd that the permissions would vary. It seems that it should be the same, unless we actively do something to change them. Just odd. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
