[packagekit] Multiple entries to WhatProvides and SearchFile

[Richard Hughes]

On 23/09/2009, Richard Hughes <hughsient at gmail.com> wrote:
> Well, in the case I'm suggesting here, no, I just don't want to break
> API in a stable series (adding API is okay) -- but you do need to put
> a limit to the amount of demarshalling and marshalling we're doing for
> the sake of API purity. In 0.6.x we'll make more stuff STRV rather
> STRING with delimiters.

In 1a51be0c2061c28361acf77196c6d06165b28412, I've added the following
comment to SearchName, SearchDetails, SearchGroup, SearchFile and
WhatProvides:

---
NOTE: On some backends an OR search can be specified by delimiting
each value with &, so this query would become games-text&games-gui.
It is recommended that front-end clients do not depend on this
functionality at this time.
In future versions of this specification the values argument will
become a string array (and no delimiters), and all backends will have
to accept multiple requests.
In this instance the failure to find one of the values would not be
fatal, but the failure to find all of the values would be fatal.
---

So, if you want your backend to support multiple OR requests, then
please make it split the search string on the '&' delimiter. It's
harmless to add now, and I've done it for yum. If you don't, that's no
problem, but the backend might stop working when we fork 0.6.x (some
months away).

Richard.