Mailinglist Archive: opensuse-factory (626 mails)
| < Previous | Next > |
Re: [opensuse-factory] Zypper behaviour - install/update as many packages as possible?
- From: Stephan Kulow <coolo@xxxxxxxxxx>
- Date: Mon, 3 Mar 2008 09:36:09 +0100
- Message-id: <200803030936.09808.coolo@xxxxxxxxxx>
Am Montag, 3. März 2008 schrieb Alex:
but with the distupgrade algorithm.
you want to use factory if not to report bug reports if kde or gnome crashes?
kdelibs-doc = because you want documentation from KDE. This is not to be
confused with kdelibs3-devel-doc, which is indeed only for developers.
The 1.9GB won't be dominated by kdelibs3-doc, but rather by packages being
rebuilt as we checked in a new bash. We're still trying to find a good answer
how to rebuild the distribution consistently and not requiring a 2GB download
every week. And it's not zypper's fault, any correct package manager will have
downloaded all these "same version" package - as they have a higher release.
Beside bash and perl-base of course.
Greetings, Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
1. When doing a factory update, zypper always insists on updating a fewThere is a bug report about that one. It has nothing to do with the solver,
packages which definitely are already installed in the newest version. E.g.
for bash or perl-base (and quite a few other packages), zypper with every
update reproducably installs the same version of this packages over and
over again.
but with the distupgrade algorithm.
You can lock the package, try man zypper
2. Dependancies: Are there plans when a less greedy solver stragegy will be
implemented? Right now, everything which is "recommended" will be
installed, or pulled in when doing an update. Thus every factory update
takes much time to download, it takes unnecessary disk space, and basically
makes handling a clean and up-to-date factory system a pain.
Why should I as a non-developper need gdb? Or kdelibs-doc andgdb = because the crash dialog will create a backtrace for you and why would
you want to use factory if not to report bug reports if kde or gnome crashes?
kdelibs-doc = because you want documentation from KDE. This is not to be
confused with kdelibs3-devel-doc, which is indeed only for developers.
PolicyKit-doc? Or Java 1.5 besides 1.6? Why do I need a complete 32bit KDE332bit KDE3 = because you might want to view flash sites.
on my 64bit KDE4 system? And so on.
I'm just complaining because right now a simple factory update on my lean
system has resulted in an 1,9 GB / 3h download as proposed by YaST, simply
because zypper deems it necessary to 1) re-install already installed
packages with the same version and 2) install dozens of additional packages
I don't need, and keep on deinstalling all the time.
The 1.9GB won't be dominated by kdelibs3-doc, but rather by packages being
rebuilt as we checked in a new bash. We're still trying to find a good answer
how to rebuild the distribution consistently and not requiring a 2GB download
every week. And it's not zypper's fault, any correct package manager will have
downloaded all these "same version" package - as they have a higher release.
Beside bash and perl-base of course.
Greetings, Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |