Ramces Tampo-og Red wrote: > Dale <[email protected]> writes: > >> Tasytea has a good idea on using sets if you prefer that way. I rarely >> use sets but a lot of people love them. It does have benefits but it >> just isn't for me. >> > I am actually very interested with sets. I haven't read enough about it > though. But I think I will try it out, it might be a neater way of > dealing with packages. > >> Hope that helps. >> >> Dale >> >> :-) :-) >> > It certainly did! > > Cheers :-) >
If sets were available when I started and I used from the beginning, I may like using them more. I'm just so used to doing it the way I've done it for ages that I don't use them. I did at one point when, I think it was KDE anyway, was making some major changes and I updated everything but KDE and only updated KDE when I felt there was a more stable release. May have been the KDE3 to KDE4 mess. If you start using it now, you may fall in love with like a lot of others have. On the --oneshot option, I get all my stuff installed and before I do my first update, a couple weeks later, I add the option to make.conf. Then if I want to install something that I use, I add --select y so it adds to the world file. As a starting point, this is my emerge defaults from make.conf: EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v --quiet-build=y -1 --unordered-display" That generally gives me a stable system even tho I run unstable on a lot of packages. You can add or remove as you see fit. May make a good starting point is all. You may also want to look into the following options in make.conf if you haven't already: MAKEOPTS FEATURES PORTAGE_NICENESS PORTAGE_IONICE_COMMAND All those are good to set but it depends on your system what to set them at. Generally, CPU abilities and memory determine that. Dale :-) :-)
