Dale <[email protected]> writes: > EssenSea wrote: >> Dale <[email protected]> writes: >> >>> 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. >>>> >>>> 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 >>> >>> :-) :-) >> Thanks for your sharing. >> >> Seems we have some little different idea about how to organization the >> make.conf file. And I'm prefer to keep it as simple as possible, and all >> config should be measure-count againisted to specific pkg though >> package.use/, package.env/, env/, and some other directions under >> /etc/portage/. >> >> Considering of my hardware, I'd like to thought EMERGE_DEFAULT_OPTS >> seems unnessary for me. >> >> Thanks for let me know a different way to manage portage system. >> > > There are a lot of different use cases out there. I'm on a desktop > system that I built like a tank. Massive cooling on everything. > Compiling isn't a problem on my system. If I were on a laptop, I'd use > different settings, most likely a binary distro. I'd likely have to. > > The setting in make.conf for emerge defaults is not the same as what > goes in package.use etc. The emerge defaults is just to save you from > having to type in options on the command line you always use anyway. > You may want to read up on exactly what it does. > > Dale > > :-) :-)
I'll try it at least with "with-bdeps" and "verbose", thanks for recommendation.
