Duncan <[EMAIL PROTECTED]> skribis: > I /always/ do an emerge --pretend --update --deep world run first,
I use 'emerge -1NuDv world -p' then strip the '-p' if I wish to proceed. I have buildpkg in my features, as well as portage logging. But for a full upgrade to ~amd64 I would add -e and --tree to the flags, to let me see more clearly how packages are being selected, and to let me prune branches via USE flags. These days I run ~amd64 by default, but with the glibc from amd64. I found cups and the whole apache-php-subversion thing difficult to manage as ~amd64 so I also use the amd64 version there. I started as amd64 but when I went to ~amd64 I did all the emerging manually, mainly because I was unfamiliar with what to expect from 'deep' merging, that far back. It was tedious, the way I did it, which was basically to make a list of packages and check them off. Now I would probably examine the tree listing check off branches at a time. -- [EMAIL PROTECTED] http://www.chemoelectric.org Esperantistoj rajtas skribi al [EMAIL PROTECTED] 'And now we're going to go try to comfort people in that part of the world.' -- Bush, referring to the southeastern U.S.
pgpV3EeRKIgqm.pgp
Description: PGP signature
