> > That doesn't mean you can't play with it, though. Just pull it down > > and compile it. It's rather frustrating, but it's good > practice, no? > > Who doesn't like compiling kernels on a 166MHz SPARC? > > > > ACCEPT_KEYWORDS="~sparc" emerge -f --oneshot gentoo-sources > > > > should get you the latest 2.6.15-r5. Tweak command line as > needed for > > other versions. > > Please don't use ACCEPT_KEYWORDS, it's generally bad, you've > got package.keywords (man 5 portage) as a better solution. > That said 2.6 kernels don't work fine in the stability > department, lately it seems only SBUS-based machines are the > ones affected. > http://www.gentoo.org/proj/en/base/sparc/sunhw.xml is a work > in progress hardware compatibility list where you can check > how things are going on the 2.6 front. > Of course it's still incomplete and feedback is welcome. > Don't say "excellent stability on X" unless you really did > extensive tests.
If you want Portage to actually manage a package, yes, I agree completely, you should NOT use ACCEPT_KEYWORDS. If you just want to use portage to grab the files for you (-f --oneshot), then, heck, just throw in ACCEPT_KEYWORDS. You'll still have to manually move things around and compile them, so where is the problem? If he *did* put "~sparc" in his package.keywords file for gentoo-sources, then he would be, in effect, telling portage that he specifically wants to be able to use the ~ versions and he accepts the responsibility thereof. And Portage will then dutifully keep him updated on all new updates to this package. How else would you "beta test" a package? I've been using this method for about two years and I have found it to work well for me. If I really want to use the package later on, I put it in the correct package.* file and make it "official". On a second point, thanks for the above HCL pointer. I'll add notes on my U30 this weekend. Bill -- [email protected] mailing list
