Bug 28923 - Wildcards for PackageKit
Summary: Wildcards for PackageKit
Alias: None
Product: PackageKit
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium enhancement
Assignee: Richard Hughes
QA Contact:
Depends on:
Reported: 2010-07-05 14:41 UTC by Matthias Klumpp
Modified: 2018-08-21 15:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Matthias Klumpp 2010-07-05 14:41:38 UTC
It would be very important for me to be able to use wildcards in PackageKit's search terms. For example on a Debian-based machine
 $ pkcon search file '/usr/lib/libogg.so.'
finds the right package containing a version of libogg.
The same on Fedora does not throw any result, cause the Yum backend needs a more specific search command than Apt requires:
 $ yum provides '/usr/lib/libogg.so.'
does not find anything, but
 $ yum provides '/usr/lib/libogg.so.*'
using the asterisk as wildcard, does find a package. If I try to submit a string containing an asterisk using pk_client_search_files_async(), PackageKit does not process the command and throws a warning about "Invalid search containing '*'".
This causes applications using PackageKit to find a package on some distributions and on some others not although it is avaliable. (Depending on the backend PKit uses)
It would be great if wildcards could be submitted to the backend if it supports them. (Otherwise a fallback would be nice) I think most of the packaging tools support wildcards, so why not make PackageKit able to use them? (I think not only me but also a lot of other people who use pkcon in scripts would be happy about this option)
Comment 1 Richard Hughes 2018-08-21 15:52:48 UTC
We moved the upstream bugtracker to GitHub a long time ago. If this issue still affects you please re-create the issue here: https://github.com/hughsie/PackageKit/issues
Sorry for the impersonal message, and fingers crossed your issue no longer happens. Thanks.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.