https://bugzilla.novell.com/show_bug.cgi?id=342600
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=342600#c2
Ján Kupec changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |schubi@novell.com, kkaempf@novell.com,
| |dmacvicar@novell.com, ma@novell.com
Status|NEW |NEEDINFO
Info Provider| |dmueller@novell.com
--- Comment #2 from Ján Kupec 2008-01-08 08:48:34 MST ---
Unfortunately, currently we don't have a way to identify "update repositories"
and any repository is potentially an update repository. What we could do in the
current situation is to quick-check all of the repositories for change since
the last update (a few second operation).
But whether we do have "update repos" or not, what about a use case where user
makes changes to the system using applications other than libzypp (rpm, yum,
smart, ...)? Then a mere check for a change in the repository is simply not
enough and a normal solver run on a fresh metadata is needed.
As for the refresh/rebuild phase, it happens only if the repo changes. So
unless it is changed, zypper update just reads the packages and solves, no
refresh. This is still slow ATM, but much less than 2 min on a common machine
and a work is being done in libzypp to still improve it.
So unless i'm wrong or i misunderstood you, i'd close this request.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.