https://bugs.kde.org/show_bug.cgi?id=390911
Michał Dybczak <michal.dybc...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michal.dybc...@gmail.com
--- Comment #6 from Michał Dybczak <michal.dybc...@gmail.com> ---
I also find this a big issue and I really thought once that Discover got stuck
or something.
As to solution, a usual update bar and "show details" list with "GUIed terminal
output" (Octopi or Pamac do that correctly) would do the trick but that's just
one of many possible solutions.
I think that packages to update shouldn't be tied to their own progress bars
like it is now. Upon hitting "Update" should open a new update area (progress
bar, info bar or whatever) showing what it's doing. Let the package list be the
list. This joined functionality is not working well in that case.
I frankly doesn't understand how it works. In terminal output is very clear, at
least on pacman side (Arch based systems) so we get shown each package and
their download progress bar one by one and once it's done, similar thing for
update progress and additional stuff. As I recall apt is doing it similarly.
My question is: if the update process is sequential, why packages on Discover
list get downloaded simultaneously?
Many simultaneous process are in fact slower then when done one by one, at
least it's often true to operation on files so I get the same feeling when
everything is downloaded at once. Maybe it's just psychological effect but at
the moment Discover creates very unease and confusing feeling during update.
And there is a matter of not asking for root credentials... Has someone filed a
bug for it? I cannot trust Discover without it and it feels like exploit...
--
You are receiving this mail because:
You are watching all bug changes.
