Mailinglist Archive: zypp-devel (148 mails)
| < Previous | Next > |
Re: [zypp-devel] api proposal for locks
- From: Josef Reidinger <jreidinger@xxxxxxx>
- Date: Fri, 28 Mar 2008 13:31:52 +0100
- Message-id: <47ECE538.2010101@xxxxxxx>
Michael Andres wrote:
Ok, so I only make seriazeble and deseriazable of PoolQuery (may I use >> and <<?)...and add saveQueriesToFile and LoadQueriesFromFile functions which move between container(of queries) and file. Rest of handling with locks I relinguish to pool (like make locks container, adding and removing from container or locking solvables from queries). Is this what you mean?
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
On Thu, Mar 27, Josef Reidinger wrote:
Hi,
I'm sending my proposal for locks API in the attachment. See FATE #120118 and [1] (locks).
The attachment contains io api for locks file and locks-to-pool bridge. Also some functions telling which Resolvables a lock or several locks cover.
question about C++ (function addLocks). I need distinguish between container that contains resolvables and locks. Is this possible in C++? (like Collection<Lock> and Collection<Resolvable> in java?)
some ideas how to solve the issue with support of regexes or wildcards in the locks file:
Instead of class Lock: Maybe we should think about save/restore queries.
- A (locks) file contains a set of queries. We restore these queries from a file.
- Executing the set of queries then leads to a set of solvables.
- We can execute any algorithm on these solvables. If the queries came from zypp.locks, we can e.g. lock these solvables.
Ok, so I only make seriazeble and deseriazable of PoolQuery (may I use >> and <<?)...and add saveQueriesToFile and LoadQueriesFromFile functions which move between container(of queries) and file. Rest of handling with locks I relinguish to pool (like make locks container, adding and removing from container or locking solvables from queries). Is this what you mean?
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |