Mailinglist Archive: zypp-devel (116 mails)
| < Previous | Next > |
Re: [zypp-devel] ZYpp lock - where don't we want it?
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Tue, 12 Jun 2007 17:08:54 +0200
- Message-id: <20070612150854.GA27503@xxxxxxxxxxxxx>
* Jan Kupec <jkupec@xxxxxxx> [Jun 12. 2007 16:38]:
> Where we don't want a zypp lock?
We should remove the global zypp lock alltogether and
move to more fine grained locks based on state changes.
Currently I see the following state changes
- repo added / removed
- cache changed (due to repo add/remove/update)
- system changed (transaction in progress)
For example, a transaction must only locks those repositories
which are part of the transaction. But I don't see the need
to lock the metadata cache during a package transaction.
Maybe I'm too optimistic here ...
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> Where we don't want a zypp lock?
We should remove the global zypp lock alltogether and
move to more fine grained locks based on state changes.
Currently I see the following state changes
- repo added / removed
- cache changed (due to repo add/remove/update)
- system changed (transaction in progress)
For example, a transaction must only locks those repositories
which are part of the transaction. But I don't see the need
to lock the metadata cache during a package transaction.
Maybe I'm too optimistic here ...
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |