[packagekit] PackageKit Collections
tim.lauridsen at googlemail.com
Sat Sep 13 23:19:03 PDT 2008
Anders F Björklund wrote:
> Richard Hughes wrote:
>>> Now, if I replace the repo with '[meta]' then I now get two identical
>>> package_ids whereas before they would differ in their "data" section:
>>> This is not good, since the package_id in PK must be unique for
>>> each ?
>>> And if I remove a dupe, then I'm not sure which one the id refers
>>> to ?
>> Exactly, the PackageId _must_ be unique.
> Another thing I discovered was that a version of "0 at noarch" didn't
> sit all too well with the current regexp for splitarch in Smart, so
> it wasn't able to find details about the packages from PackageKit...
> So now the comps Loader has been taught to use "0-0 at noarch" instead.
> Doesn't really matter, other than it'll show as "0-0" instead of "0"
> The pattern Loader already featured real data (e.g. 11.0-110.3 at i586)
> If the meta flag is moved to the pkg info rather than the repo/data,
> would it be OK to keep the ^ prefix in the name of the package_id ?
> PS. How is PackageKit going to handle multiple operating systems,
> for when just having the arch isn't good enough ? ("os" needed)
> PackageKit mailing list
> PackageKit at lists.freedesktop.org
I working on the yumbackend code now.
"kde-desktop;meta;meta;meta" as package id for a metapackage for now,
because the version,arch,repo don't make any sense for a metapackage.
and the 'meta' is easy to detect.
More information about the PackageKit