Re: new criterion proposal: Graphical package managers

[Frantisek Zatloukal]

On Thu, Nov 4, 2021, 11:40 Kamil Paral <kparal(a)redhat.com&gt; wrote:

>  I'm not sure if you understood it correctly (or if I even
> expressed it
>  correctly). The operations are of course executed sequentially, always
>  (that's how our package managers work). But they can be *scheduled*
>  concurrently, i.e. you can install GIMP, and before it is downloaded and
>  installed, you can also schedule installation of Inkscape. I think this is
>  not an unusual use case, to schedule several operations at once. E.g. I
>  just installed a new system and want to install my favorite applications.
>  Or I decided that I want to play a different game, so I hit Install on
>  OpenArena and also click Remove on SuperTuxKart.
>
>  Is this really what you are against, or have you understood it
>  differently? I can try to phrase it better.
>  
Yeah I understood it correctly. I am not saying it's not a valid use case,
just that I don't think that it's a common enough use case to be made
blocking.

>  
See my response above. Imagine that we'd ensure only the
first dnf
> operation works correctly, but any later one can blow up. Why would we want
> to allow that with a graphical package manager?
>  
You can't schedule multiple dnf operations at once. Doing a single
installation, waiting for it to finish, then doing another is something you
can do with dnf and something that I'd block on with graphical package
managers. Scheduling multiple tasks without waiting for them to finish one
by one is something that I am against blocking on.