On Wednesday 20 June 2012 08:43:00 Klaus Kaempf wrote:
* Christoph Thiel
[Jun 19. 2012 16:02]: On Tue, Jun 19, 2012 at 03:58:17PM +0200, Klaus Kaempf wrote:
Are there alternatives to a 'zypper' call ?
We are talking about https://github.com/opscode/chef/blob/master/chef/lib/chef/provider/packag e/zypper.rb
One way of improving this, would be to use libzypp ruby bindings instead of calling to zypper. Not sure if this would solve the service refresh issues.
Probably not since zypper is 'just' a cli frontend to libzypp.
Well, it's not a bug, it's designed that way. If zypper would not call ServiceRefresh, it would not happen. But zypper intentionally does a service refresh before refreshing the repos. It is not enforced but libzypp, so it would be possible to solve this 'zypper-only' (via CLI or ENV).
However, if we assume that all package operations are performed via zypper, operating directly on /var/cache/solve + libsatsolver (resp. libsolv) could be an alternative.
That's basically the same as using 'zypper --no-refresh info'. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX Products GmbH, Development, ma@suse.de GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer, HRB16746(AG Nürnberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org