On Tue, Apr 01, Josef Reidinger wrote:
If there is a 'complex' query that hit the package (name:f*o), the package will continue to be locked until the user changes the 'complex' query.
Maybe better for easier detect ui (created libzypp, not handy by user) lock can be special attribute added to query which has also be written to file during serialize and libzypp after session (or after confirm lock etc.) can remove only query with this argument. So ui can use more complicated locks
Hmm. If we want to somehow classify locks/queries and save this to a file, we could think about supporting tags(keywords): (YAST-SWSINGLE) lockspec... // generated by sw_single lockspec.. // by user (mygames,mykde) lockspec.. // by user, tags assigned (mygames) lockspec.. // " -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org