Mailinglist Archive: zypp-devel (92 mails)

[Katarina Machalkova <kmachalkova@xxxxxxx>]

> > A new concept is
> > needed here. I agree at least for patterns, being able to see packages
> > one by one is really useful, I use it a lot, but I would call it "related
> > packages", and not the content of the pattern itself.
>
> Yes, and that is what the user wants to see.
> "What will be installed/deleted if I select/deselect this"

Cool :) That's what I was asking about in the beginning: 
If install_packages() method is deprecated, how to collect all these 'related 
packages' from the zypp pool in order to present them to the user? Which 
method to use? 
I would really appreciate some example of the code, or a link to related 
developer documentation
And btw, to see packages one by one is imho useful also e.g. for languages, as 
I was already pointing out in bug #265826 

> > The function is deprecated for anyone using the Pattern API.
> > PatternContent is allowed to do nasty things because it assumes anyone
> > using PatternContent is a nasty application ;-), we should probably move
> > that "mini-solver" to the zypp/ui directory.
>
> It does not exists anymore in 10.3 cause none use it, or the use has no
> effect anymore.

If you grep yast2-qt (ncurses, gtk) code for PatternContent and 
install_packages(), you will certainly find some usage of these functions, so 
it is wrong to assume no one uses it. 
Therefore, we either need to keep the old concept (and move it somewhere else, 
if appropriate), or come up with a new alternative all UIs would be able to 
use.

B.
-- 
   \\\\\              Katarina Machalkova    
  \\\\\\\__o          YaST developer
__\\\\\\\'/_          & hedgehog painter