DUH- I fully understand the point of Cooker - I've been steadily using it since 7.2 - and I see the immense value in it as a test bed.
All I mean is - there are some periods when Cooker is fully non-usable (when it's in transition) and other times when it can be installed - with (of course) the teething problems expected with certain packages. It would be nice to know when Cooker (as a whole) is broke or when it can at least be installed and tested. I understand that some people only use selected RPMS from cooker - I frequently RSYNC the tree and attempt installs on various hardware to test the new changes. There are obvious times which I can see (from the CHANGE mailing list) that things are in transitions (like when KDE 3.01 is being rebuilt under GCC 3.1) - and I have to wait until the core RPMS are all synced up - not a problem. Just like other development efforts - there usually are indications when a major change is underway - and explicit notes as to what to expect (like early/alpha release - only for developers, etc.) As far as I understand (Please correct me if I'm wrong) - Cooker is not ONLY for developers, but also intended for advanced users and crash testers. Thanks anyway for your comments. R.Fox On Wed, 2002-05-29 at 09:06, Tom Badran wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wednesday 29 May 2002 7:33 pm, Robert Fox wrote: > > I think this is great - but as previously suggested - there should be a > > method to let people know when it is SAFE to try and install Cooker and > > when to STAY AWAY. > > This would save some precious time . . . > > Its never "safe" the safe cookers are the mandrake releases. Thats the point > of cooker, to fix the things so that it is safe (+new releases of software > etc etc) > > Tom > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > > iD8DBQE89H33XCpWOla2mCcRArdMAJ4iPaZw8zfYl7RM6JXo+qoim5W/6gCdGbiI > 8MfbcAKQDra4XINjkzkZyc0= > =1QxH > -----END PGP SIGNATURE----- > >
