On Saturday 15 November 2008 20:53:33 Carlos E. R. wrote:
On Saturday, 2008-11-15 at 07:44 -0600, Rajko M. wrote:
On Saturday 15 November 2008 07:43:26 am Dave Plater wrote:
Something like k3b does, if another application like kiocd has control it gives you the option to kill it. Nice, you should put in an enhancement request and post the number so as I can vote.
Not good. Killing another application using software database can be dangerous. Joy of having instantly available Software Management can be spoiled with broken state of the system ;-)
A normal kill is really a kind request to do suicide, and the application can refuse to die. Thus a normal "kill" would not destroy data, or should not. The package management tool would have time to close files and exit.
This is possible if you are in package selector, but if the transaction or refresh is running, this is in principle impossible in short time.
And of course, some more graceful way could be designed. Both YaST and the applet use the same database and libs, so there could be a mechanism to tell the other app to get out of the way, or perhaps to collaborate: after all, if it is updating the database, perhaps it is wise to wait till the other finishes and be told when to continue automatically.
The current lock is all-or-nothing. There is an experimental implementation of read/write locking, but this is not enabled in 11.1. Anyway, I'd like to avoid overengineering the solution as there is no right way to fix all the possible scenarios. Stano -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org