Mailinglist Archive: zypp-devel (230 mails)
| < Previous | Next > |
Re: [zypp-devel] Selectables and 'candidate'
- From: Michael Matz <matz@xxxxxxx>
- Date: Wed, 27 Feb 2008 15:42:02 +0100 (CET)
- Message-id: <Pine.LNX.4.64.0802271539150.20583@xxxxxxxxxxxxx>
Hi,
On Tue, 26 Feb 2008, Jano Kupec wrote:
Always doing a solver run would be the best. Currently the solver can be
configured towards certain modes/policies. One of them simply tries to
update all packages to the newest version (to the extent possible, i.e. it
won't give you a non-installable solution). That should be mostly what
you want when you just call "zypper lu".
(note: this is not the same as a dist upgrade though)
Ciao,
Michael.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
On Tue, 26 Feb 2008, Jano Kupec wrote:
too curious, we need to make a solver run and see what did the solver choose
to present it to the user (or should we always make a solver run to see if
there are any updates for the installed resolvables?).
Always doing a solver run would be the best. Currently the solver can be
configured towards certain modes/policies. One of them simply tries to
update all packages to the newest version (to the extent possible, i.e. it
won't give you a non-installable solution). That should be mostly what
you want when you just call "zypper lu".
(note: this is not the same as a dist upgrade though)
Ciao,
Michael.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |