Shawn Grover said: > The only issue with this is that Apache2 is also considered unstable (it's > masked). So, by removing the "~x86" from the ACCEPT_KEYWORDS, we will end > up installing Apache 1.x. Not a big deal. There is no real reason I'm > trying to run Apache2 (other than it's has newer features/patches > applied). > I'll go through this exercise tonight - It only takes about 30 minutes to > emerge Apache / mod_php.
You can use "~x86" on a per-package bases if you want. The command: ACCEPT_KEYWORDS="~x86" emerge apache -p should tell you it's going to emerge apache 2.0.46 as that is the latest 2.0.x release. It can get a little annoying sometimes if you have lots of "~x86" packages installed but you don't want the whole system that way because when you do a 'emerge -Duv world' it will probably try to downgrade any packages that were installed using "~x86". I created a script that takes a list of packages that I have installed using "~x86", does an 'emerge sync' and then uses sed to replace "~x86" with "x86" in those ebuilds. That way portage will think those packages are really stable. An example for apache would be in /usr/portage/net-www/apache/apache-2.0.46.ebuild, I replaced the line: KEYWORDS="~x86 ~ppc ~alpha ~hppa ~mips ~sparc" with: KEYWORDS="x86 ~ppc ~alpha ~hppa ~mips ~sparc" That way, I don't have to worry about setting the "~x86" keyword when I want to install it. That line needs to be modified every time you do a 'emerge sync' because it will over-write that file, but my little script does all the work for me. There might be a better way, but I found this system I wrote out works for me. I'm really busy at the moment, but I will post that script as soon as I can :) Cheers, -- Trevor Lauder Web: http://www.thelauders.net E-Mail: [EMAIL PROTECTED] Resume: http://www.thelauders.net/resume/ Gentoo Linux Powered "Any intelligent fool can make things bigger and more complex... It takes a touch of genius -- and a lot of courage to move in the opposite direction." -- Albert Einstein
