Mailinglist Archive: zypp-devel (116 mails)
| < Previous | Next > |
Re: [zypp-devel] ZYpp lock - where don't we want it?
- From: Jan Kupec <jkupec@xxxxxxx>
- Date: Tue, 12 Jun 2007 16:57:15 +0200
- Message-id: <466EB44B.9040606@xxxxxxx>
Stanislav Visnovsky wrote:
> Dňa Ut 12. Jún 2007 16:38 Jan Kupec napísal:
>> 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)
>
> You need to make sure that the parsers are not hard at work at that point.
The function to check for an existing zypp lock could be used for that
cases, see below.
>> 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.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> Dňa Ut 12. Jún 2007 16:38 Jan Kupec napísal:
>> 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)
>
> You need to make sure that the parsers are not hard at work at that point.
The function to check for an existing zypp lock could be used for that
cases, see below.
>> 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.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |