Mailinglist Archive: zypp-devel (230 mails)
| < Previous | Next > |
Re: [zypp-devel] Re: RFC: ZYpp application layer comments
- From: Jan Kupec <jkupec@xxxxxxx>
- Date: Fri, 08 Feb 2008 10:41:03 +0100
- Message-id: <47AC23AF.2050505@xxxxxxx>
Michael Matz wrote:
I'm all for it, then the implementation of the libzypp API will use what
sat solver provides, that's great. If there will be something missing in
the sat solver to implement the needed API in libzypp, we can add what's
needed to sat solver. The most imporant thing is, that the UIs have it
and don't need to code it themselves.
jano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
Now for searching.
I have no opinion on the libzypp API for searches, but I can tell you what
the satsolver library will provide (and partly provides already):
It has a generic repo_search function. The results will be given to you
via a callback function. It will accept strings and numbers, searching
in one or all solvables, in one or all attributes, for substrings, globs
or regexps, case sensitive or case insensitive. Via the callback you will
be given the information of which solvable matches, in which attribute,
and what the value of it is.
Using the repo_search function will be much faster and take much less
memory than implementing the searches by hand in libzypp (those would need
to retrieve all attributes one by one, or (even worse) cache that data
itself).
I'm all for it, then the implementation of the libzypp API will use what
sat solver provides, that's great. If there will be something missing in
the sat solver to implement the needed API in libzypp, we can add what's
needed to sat solver. The most imporant thing is, that the UIs have it
and don't need to code it themselves.
jano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |