Caleb Tennis posted <[EMAIL PROTECTED]>, excerpted below, on Tue, 04 Apr 2006 06:38:39 -0400:
> I think historically we were much more bleeding edge with our stable KDE > versions than at the moment, but if you've spent any significant time > playing with 3.5.0 or 3.5.1, I think you would agree that they are > terribly less stable than 3.4.3. But in a few weeks I think 3.5.2 will be > stable and it will all be behind us. I have, and it seems decently stable here. (Well, there's that expat upgrade like a day after I had finished compiling 3.5.2, but some things can't be helped and that upgrade would kill 3.4.x as well, if I'm not mistaken -- may I suggest a KDE 3.5 and the expat upgrade go stable together?) In general, however, fairly stable. However, part of that may well be that I'm running ~amd64, not x86, with its many sub-archs hardware-wise and the problems some of them have. As amd64 is fairly new, there are only a couple of hardware subarchs for it yet, and they are quite compatible, so stuff generally either works for everyone or noone. I've learned that I can safely comment out many of the calls to stripflags or filterflags, as often, the condition they are correcting for doesn't affect amd64, yet unfortunately, the calls aren't conditioned on arch as they would be in a perfect world with access to full testing on all archs right away. -- 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 in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
