Malvern Star said the following on 12/09/2011 10:36 PM:
Ordinary users do not use the command line. If I told them they had to learn to do so in order to get updates they would interpret this as an *insult*, and rightly so.
Ordinary users should not be playing around in YaST, because it is too easy for them to break other things accidentally.
I've mentioned a number of times, and rather have been other questions here in the last month that approach this issue as well, but why is it so hard to write a short script and then create a desktop item to run it? You don't need the whole of the menu of YAST. You can hand the users a constrained subset of YAST which they can run and can't get out of. I often type "yast2 sw_single" on the command line to just get the installer and nothing else appears. I'm sure there is a option for updates rather than install - go check the docs. And there are plenty of tools to permit script driven GUI-fication. Worst case its a bit of Tcl - or Tk/Perl. KpackageKit is also not "constrained". Users can add/delete software as well as so updates. So I don't see your problem. And I'll reiterate my other points about the lemming-like rush to move to 12.1. If you've got problems where you are then moving to 12.1 will just add more and more problems. What you're saying that you're trying to do makes no sense. -- "Security can be viewed like a construction scenario - build part of a road, and even if and even if you don't complete it, you still have something to drive on; build part of a bridge and you have nothing! Security is like the last." -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org