"Vladimir G. Ivanovic" <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Sun, 29 Oct 2006 10:31:34 -0800:
> Yes, I am running ~amd64 (ACCEPT_KEYWORDS="amd64 ~amd64" > in /etc/make.conf.) I also changed to the 2006.0 profile, although I've > forgotten how I did that. FWIW, I update profiles when or somewhat before they go public, so have been on 2006.1/desktop for some time now. I /think/ it covers changing profiles in the manual, either that or in a howto somewhere, but normally, it's just make sure you are up2date where you are (emerge --sync, emerge --newuse --deep --update world, revdep-rebuild, preferrably at least look at emerge --pretend --depclean and either unmerge the ebuilds or add to world as needed, then do another revdep-rebuild), point your /etc/make.profile symlink at the new profile desired, and do another emerge --newuse --deep --update world to update to anything the new profile changed. Of course, those emerges should be previewed with --pretend --verbose first, to see what it's going to do, so nothing unexpected hits you in the face. That's PARTICULARLY true with the first one after updating the profile symlink, as until you start merging stuff, no harm done and it's easy to reverse if necessary, but it might not be so easy after you start merging stuff. Not all profile updates are routine, however. 2006 has been pretty smooth, but for us folks on Gentoo/amd64, the 2004.3 and 2005 profile updates were rather major, as they involved rather large changes to the way multilib was handled, and if the update wasn't done following the instructions precisely, it could (and did) leave people with broken systems. Some of them worked their way out of the mess. Others gave up and decided it was easier to start over from a fresh stage install. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- gentoo-amd64@gentoo.org mailing list
