YaST Control Center -Manage Software

English Applications
1

Some noted bugs with YaST in openSuse 11.2:

Whenever you add/remove packages via YaST control center, after the package is installed or removed YaST reruns suseConfig for several services (that are not part of the package installation/removal you just made) and then terminates taking you back to. It would be better if the application would take you back to the software mgr interface and then run suseConfig only for whatever services were installed/removed rather than everything.

If removing a package and selecting Selected by the User for the action, YaST installs recommended replacement packages anyway.

The help system associated with the various configuration tools within YaST control center needs improvement and more detailed information to be very useful.

2

IMHO these are two things.

  1. The fact that after installation YaST nowadays does not ask if you want to install/remove more or not (as it did in earlierr versions), but simply takes it for granted that yoy are done (which in my case is very often nnot true). From this you may cortrectly coclude that this behaviour annoyes me. There is almost for sure a place where you can vote for the returm of this feature, but I do not know where.

  2. the runing of a complete suseconfig instead of only partly. I think this is because the fact that susconfig must be run for a particular subject must then be found inside the installed/removed packages, which is prone to errors from the packagers. In any case it does not take to much time.

3

Looks like somewhere internally it was decided that it was a desired functionality for Software Management to close itself down after its done. (I agree with you and personally think it’s rather odd and you have no way to tell if it crashed or finished it job if you left it running in the background)

On the bright side, in 11.2 there is an option to configure it’s behaviour somewhat. Start up ‘/etc/sysconfig editor’ (also found in YaST) and in the treemenu on the left unfold **System > Yast2 > GUI ** and select the option ‘PKGMGR_ACTION_AT_EXIT’ and change the behaviour to either restart or summary instead of ‘close’.

4

For #2 I personally don’t want suseConfig editing config files I’ve already tweaked for something that wasn’t in the list of packages I installed. As a developer I know the behavior of the applet can be changed, I just hope the developers of YaST will see this and work on improving the way the control center operates (which I’m sure they are working on the next release anyway). :wink:

5

Nice to know. I know it was asked for strongly when the behaviour of the new YaST became clear. Did not know it is there, down in an obscure place.

6

Since this bothers me too, I found the place in Bugzilla to vote (I think): It’s bug 539387 [Qt4-Pkg] PKGMGR_ACTION_AT_EXIT accessible from YaST Software Management: https://bugzilla.novell.com/show_bug.cgi?id=539387.
I’ll put my vote in - let’s all use our democratic right to be ignored :-)…

7

I am sure I already voted for it during some pre-release Milestone version. Ther was a lot of upheaval at that time.

I am afraid that all that came out of it was this hidden away parameter Axeia found.

8

There are only 7 votes listed for this issue and it was assigned in October this year. Maybe there was a new bug created?

Interestingly enough, the ncurses version has an option to do this, already.