Mailinglist Archive: zypp-devel (116 mails)

[Jan Kupec <jkupec@xxxxxxx>]

Where we don't want a zypp lock? Where we need read access only in
general. In particular:

- listing known repositories
- search (all kinds - listing available updates falls into this
  category)
- other queries like zypper info, zypper patch-info, etc
- (other cases?)

What's to proper code to call when libzypp client wants to acquire zypp
lock? Do we support all the above already, or do we need modifications?

This list also applies to read access for non-root users. That means
/etc/zypp/repo.d/* and /var/lib/cache/zypp.db must be readable by
non-roots. (I can't think of more.)

Also, some function for checking whether other app is having the lock
would be nice for use even if we don't need the lock. Having that, e.g
zypper search could show a warning that the search result can be
inaccurate because of another app manipulating zypp data.

Cheers,

Jano
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx