On Tuesday 05 November 2013 18.34:20 Graham P Davis wrote:
On Mon, 04 Nov 2013 16:49:36 +0100 Martin Schlander <martin.schlander@gmail.com> wrote:
Mandag den 4. november 2013 17:40:29 skrev Basil Chupin:
On 04/11/13 16:05, Rajko wrote:
I had a problem with YaST Software Management that was closing after package(s) installation. Some anal-retentive, or -retentives, decided that "close" it should be and s/he/it will not move from this idiotic position.
You want something intelligent then do the editing yourself and change the setting to, "summary" because the anal-retentive(s) will not.
Yes, it's a very bad default.
The historical reason was that previously some pop-up would appear and steal focus when YaST was done installing stuff, and some people complained about that, so YaST was made to close when done.
Nowadays with the summary or restart options, the original "problem" with the pop-up no longer exists, but we're still stuck with the bad default.
Several years ago, YaST Software Management used to have an option in the menu that you could change so that it would stay open once the installation had completed; I don't recall whether 'summary' was also an option. I'm not against the default action but wish the option to change the default was returned to the menu; I don't understand why it was removed.
/etc/sysconfig/yast2 come from nowhere :-) rpm -qf = nobody knows ## Type: list(close,restart,summary) ## Default: "close" # Set the default behavior of the package manager when package installation has finished. # Possible actions are: # close - just finish the package manager # restart - go back to the package manager, install/remove more packages # summary - display an installation summary dialog, there user can decide whether to finish or restart # The summary dialog is always displayed when an installation error has occured. PKGMGR_ACTION_AT_EXIT="summary" So to resume the default (empty) = close if everything goes smooth except when a kernel is installed a dialog box ask the user to reboot or it show summary if something goes wrong. Being not able to find the source (where's luke?) I can't determine what changes by who and when appear. It's also hard to create a nice bugzilla, have a patch proposed sr etc ... -- Bruno Friedmann Ioda-Net S�rl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org