Mailinglist Archive: zypp-devel (92 mails)

[Stanislav Visnovsky <visnov@xxxxxxx>]

Dňa Friday 24 August 2007 13:05:32 Stefan Schubert ste napísal:
> Duncan Mac-Vicar Prett schrieb:
> > On Friday 24 August 2007 11:03:39 Stefan Schubert wrote:
> >> Katarina Machalkova schrieb:
> >>> Provided that this method is really deprecated, I'm probably supposed
> >>> to use something else instead, to achieve the same goal in UI ;-) 
> >>> Could you please point me to some other libzypp method I can possibly
> >>> use, or advise me how to collect names of the packages that will be
> >>> installed once user select a pattern?
> >>
> >> This was a very quick hack and with a lot of unexpected behaviour.
> >> Now you only have to select the pattern and make a complete solver run.
> >> The solver will select the concerning packages which you will have to
> >> pick up then.
> >
> > That is exactly the point we have been discussing from the beggining.
> >
> > - ZYpp developers can't accept the fact that someone wants to look
> > pattern "contents" instead of looking the result of selecting a pattern
> > at transaction time.
>
> Hm, the "normal" user is not interested in the content of a pattern.  So
> the
> "general" UI should not provide this information in the main view.

In fact, I don't agree. I want to see what will this beast do. I don't care 
how you name it, but 'content' is pretty sound name for the thing I want to 
see.

Technically, you are right, you want to see how the dependencies will 
influence your system. But that's hard to explain in non-technical terms.

Anyway, the UIs will need to have a way to provide this information IMO.

Stano


> For that use vi :-)
> or
> xv ~schubi/Export/solvertree/kde.jpg
>
> > - UI developers insist that patches and patterns have content. While the
> > poor Patch and Pattern class have no knowledge about that, they just
> > depends on things, and the solver knows what to grab. It is
> > understandable, because the UIs were mostly "adapted". 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"
>
> > 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.
>
> Greetings
> Stefan
>
>
> --
> ***************************************************************************
>**** Stefan Schubert
> SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany
> e-mail: schubi@xxxxxxx
> ---------------------------------------------------------------------------
>---- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx