I guess the correct answer would be that it depends on several things. first- Sometimes programs just don't work. second. sometimes the os just doesn't work. usually when some major change in the os like new rpm glibc gcc etc. I am by no means an expert but I have been using it on my home computer since about 7.0. and not that i can say that there have been times that i have resorted to reinstalling the latest stable version until cooker stabilized. I would not recommend running a mission critical server on cooker, but for home use and with some understanding of sometimes things break, go for it and when you find a bug, report it in a non-offending and well elaborated manner. That is what cooker is here for.
Salane King On Thursday 04 April 2002 01:15 pm, Michael Andreen wrote: > I posted this as reply to another thread, but looks like the discussion in > that thread is over and noone is planning an answer, so here it is now, but > not as a reply. > > To: [EMAIL PROTECTED] > > On Wednesday 03 April 2002 10.29, Laurent Montel wrote: > > Perhaps you don't know but cooker is DIFFERENT from 8.2 ! > > When this is up.. It's been said that it's dangerous to run cooker, but how > dangerous is it really? > > I've been "idling" on this mailinglist for a few months now and I can't see > that it's more dangerous than always compiling and running the latest > release of everything (which I tend to be doing after a while, or > "stealing" a cooker package once in a while and get it into the stable > dist), actually it seems less dangerous since you mdk guys are more > experianced and follows the development of your packages better than me (I > guess). > > So what's recommended? Running a stable release and compiling the latest > software/ using a few cooker packages in the stable release or running a > pure cooker system? > > Michael Andreen > [EMAIL PROTECTED] -- It is illegal to say "Oh, Boy" in Jonesboro, Georgia.
