On 11/29/05, Alex Bennee <[EMAIL PROTECTED]> wrote: > On Mon, 2005-11-28 at 19:52 -0800, Mark Knecht wrote: > > > A questions though. Just because an app is not tested on AMD64, and > > hence not keyworded with amd64 or ~amd64, doesn't mean it has a > > problem, does it? It just means it's not tested, right? Or am I > > incorrect in that? > > Sure, but you it depends if you want to make all x86 (but not amd64 or > ~amd64) apps available. My personal preference is to clone the ebuilds > of stuff I want to try that hasn't got an amd keyword of one sort or > another into my overlay directory and then build them. This means my > systems is: > > * mainly stable amd64 packages > * with a selection of ~amd64 packages (via package.keywords) > * with a few cloned/overlayed x86 only builds manually editied to be > ~amd64 > > Hopefully this stops you whole system being pulled into an unstable > state.
Yes, I hope so. Since I never build with ACCEPT_KEYWORDS="~x86" but rather put all keywords in package.keywords, I've rebuilt almost all the ~x86 applications with ~amd64. I have not done the --emptytree rebuild yet and may not for the next week or two just to see how things go. Thanks for the strategies. cheers, Mark -- [email protected] mailing list
