> Also, on a sidenote... And by no means intended to start a flame war or > something like that, but how come so many stuff in cooker is broken, or > breaks things which previously worked? My fonts change from unreadably > small to horribly huge after a MandrakeUpdate, my belgian keyboard > switches from a state where it can produce a tilde to where it can't (in > X; only the tilde seems affected), stuff that used to work suddenly > doesn't work anymore, new libs which should obsolete older ones conflict > instead of obsoleting and removing them from the system, icons disappear > and after another upgrade reappear... sometimes... All of a sudden since > upgrading my kdelibs my kvirc stops working and can't be found on the > mirrors anymore either (ok, ok, I got the warning that there were > incompatibilities and clicked "force", not a good idea, but why does it > have to break in the first place?)... > > Yeah, sure, I read the disclaimer, I know cooker is not > "production-ready", but hey, I got debian boxes at home which run on the > "unstable" (sid) branch and guess what: they don't fuck up. Now I don't > want to start a distro war here, I like mandrake, but I'd like to see a > way of keeping my system up to date with the latest software releases > without slowly tearing it apart in the process. Cooker is definately not > it; too many things go wrong whenever you try to keep it up to date. > Seems like some mdk cooker packagers are just sloppy and don't even > check their upgraded packages, or otherwise I just missed some basic > howto-knowledge on MandrakeUpdate and Cooker use... I hope it's the > latter; in that case someone can enlighten me and I might learn from my > mistakes.
I moved to cooker a month or two ago and it's been a very nice ride so far, it's not much that I miss in it.. ;) Sure there are some things that get wrong once in a while, but of what I've seen they get solved rather quickly (as long as someone bothers to report it, if it isn't reported then it's hard to solve the problem since it's hard enough to find it in the <insert HUGE number> possible configurations). Just continue reporting problmes, that's what's really needed and if noone responds then complain about the lack of response since good reporting and good response is what's needed (and of course some action from the responding part) to get rid of the flaws. I can't answer on your other problems, but let's look at your kvirc problem: The latest stable release of kvirc 2 does not compile with QT3/KDE3. There is some maintaining on the 2 branch, but I don't know if they're planning to port it to kde3 and if it gets ported to kde3 it prolly won't be compilable with gcc > 3 (since I had to send in a patch to make the kvirc 3 branch compile). kvirc 3, even though it isn't released as stable yet, is a very nice client (that beats everything I've seen so far on both linux and windows) and I've been running selfcompiled versions for about 5 months now. Sure it would be nice to have this packaged for cooker (who maintained kvirc2? maybe time for me to learn how to create rpms?? ;), but it's not hard at all (if you got some experiance of compiling) to either check out the latest cvs snapshot or download a snapshot from ftp://ftp.kvirc.net if you don't want to mess with the auto* tools. I very much recommend that you do that. Sure a rpm would be nice but it require someone who maintains it. Until then the #kvirc channel on the open projects irc network is mostly friendly and helpful.. ;) Michael Andreen [EMAIL PROTECTED]
