On Fri, Feb 15, Michael Matz wrote:
Hi,
On Fri, 15 Feb 2008, Michael Schroeder wrote:
On Tue, Feb 12, 2008 at 05:38:28PM +0100, Klaus Kaempf wrote:
Well, thats bad. libzypp checked when parsing repository metadata and discarded solvables incompatible with the target system. repo_add_solv() could (should?) do this.
No, it shouldn't.
Right now, ma implemented this by nulling out the solvables which are of incompatible architecture. I'm not totally excited about this, but it should work fine (and has the benefit that for applications using libzypp nothing changes, i.e. they don't see incompatible solvables). An
Most applications dont want to see them.
alternative would have been annotating doUpgrade() (and everything else which tries to figure out update candidates on its own) with compatibleWith() checks, like I started to do.
But why even looking at packages I'm not interested in? If we want to make a feature out of shipping metadata for all archs, then we should allow to define subsets of solvables (e.g. all ppc compatible) and let the solver operate on those subsets. Each solver maintaining it's own context (arch, requested languages, whatprovides index....). -- 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