All politics aside, I am new to this mailing list, and new to the whole Cooker thing, although I have been a happy user of Mandrake for several versions now. I've tried Red Hat and Debian, but I prefer Mandrake because it makes things easiest for people who don't want to spend a lot of time researching things on the net to find out how to install them (I look forward to each new evolution package release -- have you ever tried to compile that beast? I have... on Solaris... as non-root... don't try this at home).On Sun, 2001-12-02 at 01:38, Marcel Pol wrote: > On 02 Dec 2001 00:09:25 -0600 > Lance Klein <[EMAIL PROTECTED]> wrote: > > > I "successfully" upgraded my LM80 box from 2.2.1 to 2.2.2 using > > binaries from cooker, but all the icons disappeared. <snip> > Cooker and mdk8.0 or mdk8.1 are not the same distro. > The libpng packags are different, and that's only the start. > If you want to run Cooker, then run Cooker. <snip> If there are problems upgrading to the latest superxyz-9.5.3-1mdk package and that problem can be attributed to a change in libraries, then great. But if the package installed cleanly (i.e. no --force or --nodeps) and something the package required isn't there, then there is a dependency issue. <snip> -- Anton Graham GPG ID: 0x18F78541 <[EMAIL PROTECTED]> RSA key available upon request There are three rules for writing a novel. Unfortunately, no one knows what they are. -- Somerset Maugham
The great thing about rpm (or dpkg for that matter) from a user standpoint is it helps you to avoid messing up your system. I praise package maintainers for sweating over dependency lists so I can "plug-and-play" new packages whenever something new and interesting comes along. As a user of Mandrake, I expect that running "rpm -Uvh" on a package will let me know all dependencies. If I get a never-ending dependency cycle, then I know I need to update my distribution. However, that was not true with KDE 2.2.2, and it is my opinion the package dependencies should be updated to reflect the fact that libqt2 >= 2.3.1-18 is required. Once I included the new package, everything went fine (thanks to Mr. Borntreger).
Please don't lose sight of the fact that dependency lists are of paramount importance to maintaining a satisfying user experience. Don't make people subscribe to mailing lists or search archives to find out little gems like that one.
Thanks to everyone who helped me out on this one.
-Lance
