EssenSea wrote: > As a gentoo desktop user, update pkg though emerge is my daily job. > I've set 'emerge --sync && emerge -fuDU @world' as a cron job, and > I'm insisted in doing 'emerge -avuDU @world' manully everday. > > Here's my question, I've noticed that 'emerge -avuUD @world' and 'emerge > -avguDU @world' will result in some differences, normal, 'guUD' will > result in less pkgs to be updated. And after 'guDU' finished, if I run > 'uDU', seems still some pkgs need to be updated. I'm not sure why this > is. Is someone familiar with this? > > And is there any other better way to upgrade for daily desktop mechine? > > >
My setup is a little different. I have some options in make.conf for emerge. Saves me from having to remember them all, especially the --oneshot one. This is my make.conf setting. EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=500 --keep-going -v --quiet-build=y -1 --unordered-display --jobs=16 --load-average 8" The -1 is same as --oneshot. It keeps the world file from getting filled with clutter. Once I sync the tree, I run emerge -auDN world. Over the years, that has given me the most stable system. Before using those options, I would get the occasional seg fault and such and have to emerge packages manually to fix them. My command does emerge some more packages but it results in a system where packages work better together. I'm sure others use some other set of options but it is rare that I run into problems with some package getting missed when it either should have been rebuilt or upgraded. Just thought I'd share. :-D Dale :-) :-)
