On 05/06/2010 01:47 PM, Tim Waugh wrote:
Currently system-config-printer uses these mechanisms for installing things
- PackageKit (driver packages, distribution-provided and 3rd-party)
- Jockey (driver packages, 3rd-party)
- OpenPrinting web query (driver PPDs only, 3rd party)
I hope to phase out the OpenPrinting web query mechanism in favour of PackageKit once all the pieces are in place. Similarly with Jockey, if possible.
I think the Jockey approach is still needed, as it allows to access OpenPrinting as one-stop location for querying driver availability. The OpenPrinting database can reference to drivers which are hosted at arbitrary locations. The PackageKit approach which is only based on in-package printer-driver-relation data would need a list of all driver host locations to find drivers. So if a manufacturer introduces a new driver repository, all distributions would need to add this repository to their lists.
Till