Mailinglist Archive: opensuse-factory (464 mails)

< Previous Next >
Re: [opensuse-factory] YaST/zypp dependancy handling question
  • From: Stephan Kulow <coolo@xxxxxxxxxx>
  • Date: Thu, 7 Feb 2008 08:06:27 +0100
  • Message-id: <200802070806.27505.coolo@xxxxxxxxxx>
Am Donnerstag, 7. Februar 2008 schrieb Alex:
Why were they forcibly installed in the first place??

Because they are "recommended" packages and our alpha1 solver likes
to make your system complete. As workaround edit /etc/zypp/locks and
put all packages in there you don't want to see.


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.)
As said in the Alpha1 release announcement: please create test cases whenever
you see something strange with package management. i586 packages on 64bit _is_
such a strange case.


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.
There is kdebase3-nsplugin which provides you access to 32bit flash-player and
it's installed by default and pulls in many 32bit dependencies.


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 ;) ?
We're still lacking a way to make decisions about packages persistent, this is
something to be worked on for 11.0 - for now it's a intended behaviour and you
can workaround it with /etc/zypp/locks


BTW: Is there a way of getting rid of the "bundle-language"-meta-Packages
to only install the needed rpms?
the needed rpms will be larger than the bundles, but you can easily
zypper in bundle-lang-other
zypper remove bundle-lang-kde-<$LANG> bundle-lang-common-<$LANG>

See for example my system:

The following NEW packages are going to be installed:
amarok-lang avahi-lang beagle-lang digikam-lang gwenview-lang k3b-lang
kdebase3-SuSE-lang kdebluetooth-lang kdetv-lang kerry-lang kipi-plugins-lang
konversation-lang kpowersave-lang libkipi0-lang libwnck-lang
notification-daemon-lang

The following packages are going to be REMOVED:
bundle-lang-common-de bundle-lang-gnome-de bundle-lang-kde-de

Overall download size: 33.7 M. After the operation, additional 60.2 M will be
used.
Continue? [yes/no]:

So you can install "only needed rpms", but they are actually 60M larger

Greetings, Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
References