With 11.0alpha1, I tried (for the first time since that infamous SUSE-release with ZMD ;) to use the yast Package management. I'm simply sick of "smart". However, I don't really get how zypp does the dependancy checks: It always seems to pull in way too many other packages for no obvious reasons in every update. Many of this unwanted packages can be uninstalled afterwards with Yast - seemingly without any dependancy problem, so the question is: Why were they forcibly installed in the first place?? E.g. "doc"-Packages: Yast always insists on installing e.g. kdelibs3-doc, PolicyKit-doc, readline-doc and so on. (For PolicyKit-doc, I yesterday even caught Yast installing a *.i586.rpm-package on my 64bit-system without any kind of warning, something I really dislike, because I had some nasty system failures when 32bit (binary) packages were mistakenly installed by the package management system in former times.) Yast also insists on installing a full 32bit KDE3 subsystem on my 64bit system (with all the dozens of other necessary 32bit libs), although no 32bit KDE app at all is installed. OpenOffice: I prefer a lean installation with only some parts of it, but Yast forrces me to do a pretty full install with every update (all templates, additional english language and so on). I could go on with many more examples. My question is: Am I getting something completely wrong here, or is this intended behaviour of Yast? Is this, because certain patternss are active - and if yes, how do I get rid of them? Because, what good is it to have fine-grained packages if the dependancy check pulls everything nevertheless ;) ? BTW: Is there a way of getting rid of the "bundle-language"-meta-Packages to only install the needed rpms? Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org