[zypp-devel] Updating packages
-------- Original-Nachricht --------
Betreff: Re: update stack. tasks
Datum: Mon, 31 Mar 2008 15:50:47 +0200
Von: Stefan Schubert
----------------------------------
Let me add
* Updates
- Provide a 'compute package updates' function (using sat-solver 'update_system' mode) in all zypp applications (qt, ncurses, gtk, zypper). Replacing the current loop-over-pool-finding-'newer'-packages functionality.
Libzypp supports this now: /** * Update to the newest package * * Install the newest version of your installed packages as * far as possible. This means a newer package will NOT be * installed if it generates dependency problems. * So the user will not get an error message. * **/ void doUpdate( ); Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi@suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi@suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
great! Should up -t package be replaced with this? Normally, command line tools use upgrade, so it is consistent with dup (dist upgrade) Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
It should be used for "zypper up" without any packagename in order to get the newest version of ALL packages. Duncan Mac-Vicar P. schrieb:
great!
Should up -t package be replaced with this?
There is already a SAT-solver call which fulfill this request and has to be added to libzypp only. I am working on it. Thank you for remembering :-)
Normally, command line tools use upgrade, so it is consistent with dup (dist upgrade)
Duncan
-- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi@suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Stefan Schubert napsal(a):
Klaus Kaempf schrieb:
----------------------------------
Let me add
* Updates
- Provide a 'compute package updates' function (using sat-solver 'update_system' mode) in all zypp applications (qt, ncurses, gtk, zypper). Replacing the current loop-over-pool-finding-'newer'-packages functionality.
Libzypp supports this now:
/** * Update to the newest package * * Install the newest version of your installed packages as * far as possible. This means a newer package will NOT be * installed if it generates dependency problems. * So the user will not get an error message. * **/ void doUpdate( );
Nice to have, thanks. Nevertheless, is it able to limit the set of packages going to be updated somehow? As we've been talking about it on this mailing-list recently, users often want to: * update only $add_your_favorite_repository_here packages * update only the listed packages (and their dependencies) * update all packages (maximum we can do) Is that doUpdate function able to handle such requirements? Thx && Bye Lukas
On Tue, Apr 01, Lukas Ocilka wrote:
Stefan Schubert napsal(a):
Klaus Kaempf schrieb:
----------------------------------
Let me add
* Updates
- Provide a 'compute package updates' function (using sat-solver 'update_system' mode) in all zypp applications (qt, ncurses, gtk, zypper). Replacing the current loop-over-pool-finding-'newer'-packages functionality.
Libzypp supports this now:
/** * Update to the newest package * * Install the newest version of your installed packages as * far as possible. This means a newer package will NOT be * installed if it generates dependency problems. * So the user will not get an error message. * **/ void doUpdate( );
Nice to have, thanks.
Nevertheless, is it able to limit the set of packages going to be updated somehow? As we've been talking about it on this mailing-list recently, users often want to:
* update only $add_your_favorite_repository_here packages * update only the listed packages (and their dependencies) * update all packages (maximum we can do)
Is that doUpdate function able to handle such requirements?
We will provide a generic interface that will allow you to create solver requests like: doUpdate( "foo" ); // one Solvable for_each( c.begin(), c.end(), DoUpdate() ); // a collection Schubi and I am about to get this going. This will replace the old solver.solver.addRequires etc. interface. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (4)
-
Duncan Mac-Vicar P.
-
Lukas Ocilka
-
Michael Andres
-
Stefan Schubert