Mailinglist Archive: zypp-devel (64 mails)

[Michael Andres <ma@xxxxxxx>]

On Thu, Jul 31, Jan Kupec wrote:

> Michael Andres wrote:
> > On Thu, Jul 31, Jan Kupec wrote:
> >
> > > > > As for the interface, i suggest to place the functions to ZConfig:
> > > > Take into account that our ZConfig handling is not clean, if we use 
> > > > --root. 
> > > What exactly is the problem or ambiguity?
> >
> > If the chrooted system says 'arch = s390' and the outer system says 'arch 
> > = i386': 
> > We use 'i386' but should use 's390'.
> > The same for the other settings like e.g. solver.onlyRequires. 
> > A --root systems Zconfig settings may have no effect. 
>
> Hm, that sounds like something for fixing...? Why not just read the --root 
> system's setttings? For values not specified there, use defaults, just like 
> when in '/'.

You can do this as soon as you know the --root. zypper knows it quite 
early from the commandline. YaST tells it when initializing the target, 
and that's usually quite late, even after having loaded repositories.

This is another usecase for introducing signals, so each component can 
easily monitor changes in other parts.

-- 

cu,
    Michael Andres

+------------------------------------------------------------------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862  27AC 3FB8 9E3A 27C6 B0E4
+------------------------------------------------------------------+
Michael Andres             YaST Development            ma@xxxxxxxxxx
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@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx