Mailinglist Archive: zypp-devel (148 mails)
| < Previous | Next > |
Re: [zypp-devel] New resolvable state : recommended/suggested
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Fri, 28 Mar 2008 10:06:05 +0100
- Message-id: <20080328090605.GC26135@xxxxxxxxxxxxx>
* Duncan Mac-Vicar P. <dmacvicar@xxxxxxx> [Mar 28. 2008 09:56]:
Because it should hide the actual implementation of 'pool' or how
solvables and their state are stored internally.
Remember that long-term we want zypp to be 'transaction-based',
removing the need of a huge, static, in-memory, mutex-protected data
structure holding global state information.
Right.
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
Klaus Kaempf wrote:
Then why do you recommend a iterator? On what do you want to iterate on
I'd like to reduce (to zero, actually) any loops 'over pool' in zypp
applications.
then?
Because it should hide the actual implementation of 'pool' or how
solvables and their state are stored internally.
Remember that long-term we want zypp to be 'transaction-based',
removing the need of a huge, static, in-memory, mutex-protected data
structure holding global state information.
( actually, in pool the iterator exists, but needs to be constructed
using filter iterator and status filter, this could be wrapped each
recommended I think )
Right.
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |