This behavior is extremely annoying especially when your trying to compile something that requires libraries to be installed. It was much handier to run your ./configure with yast open and then add libraries as needed to complete the configure. Instead of just removing the “Do you want to add more packages” dialog they should have made it at least a preference in the Yast Software module to let the user choose the behavior desired.
If your ticked off from this behavior let them know on this bugzilla ticket:
Re the caches: I use 2 machines for development, and am updating repeatedly. Once a repo is refreshed, restarting takes only a second. I can see when a particular repo gets refreshed while another is bypassed. So I can’t speak to slowdowns others are experiencing. Luckily for me it’s working as intended.
I really like your suggestion - like to see you post that to the bug report linked. Much better than the compromise that was debated (and IMO isn’t acceptable for the reason cited there).
Yes. Opening Yast again is a snip. It hasn’t bothered me that much that I would moan about it.
Though there is a bug for the slow responsiveness in the GUI and fix is up in the test updates - which works.
So are you saying you do not have a problem in Software Management, say filter by repo and select Packman, does it display quickly? It was taking 30 seconds for me before the fix. Obviously I mean from a 11.1 default install, and not in a development box which may be running the test updates anyway.
I have both 11.0 and 11.1 running (in various incarnations), but haven’t spent much time at all yet in 11.1. The speed I was referring to earlier is in starting Software Management; very fast unless a repo cache needs to be refreshed. Within SM, I have noticed that it can take a while to filter by a large category - Packman is a good example. Or @System; with all I have installed takes a couple minutes to load the list.
Here’s a workaround I’ve tested on 11.0, I’ll try it tonight on 11.1:
Use “/sbin/yast2 sw_single” to launch the software manager directly. I created a shortcut for my panel to do this. This avoids having a big YaST control center window around. I use “–gtk” too, it saves space.
Tick the “keep password” box when kdesu/gnomesu asks for a password.
Repositories seem to be caching OK, but if not, use the “skip autorefresh” button on subsequent invovations.
I apologise, but I just didn’t notice that “keep password” box before. Maybe the other “irritated” users have missed it too?
End result - usable, quick. I’d still like to have the 11.0 dialog box back, or one of the proposed compromises, but at least the pain is gone.
I voted for it. A exit message “all ended well” is needed. Not just an empty screen when you unlock your desktop after half an hour. And this “al ended well” could just be the old message.
