The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet...

The System and Arch are optional added filters, for example System could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system.

RPM resource cups-browsed

CUPS is a standards-based, open-source printing system. CUPS uses the Internet Printing Protocol ("IPP") and provides System V and Berkeley command-line interfaces, a web interface, and a C API to manage printers and print jobs. This package contains cups-browsed, a helper daemon to browse the network for remote CUPS queues and IPP network printers and automatically create local queues pointing to them. cups-browsed has the following functionality: * Auto-discover print services advertised via DNS-SD (network printers, IPP-over-USB printers, Printer Applications, remote CUPS queues) and create local queues pointing to them. CUPS usually automatically creates temporary queues for such print services, but several print dialogs use old CUPS APIs and therefore require permanent local queues to see such printers. * Auto-discover shared printers on remote CUPS servers running CUPS 1.5.x or older via legacy CUPS browsing. This is intended for settings with print servers running long-term-support enterprise distributions. * Broadcast shared local printers using legacy CUPS browsing (of CUPS 1.5.x) for settings with printing clients running long-term-support enterprise distributions. * Creating printer clusters where jobs are printed to one single queue and get automatically passed on to a suitable member printer. * Manual (via config file) and automatic (equally-named remote CUPS printers form local cluster, as in legacy CUPS 1.5.x and older) creation of cluster queues * If member printers are different models/types, the local queue gets the totality of all their features, options, and choices. Job goes to printer which actually supports the user-selected job settings. So in a cluster of photo printer, fast laser, and large format selecting photo paper for example makes the job go to the photo printer, duplex makes it go to the laser, A2 paper to the large format ... So user has one queue for all printers, they select features, not printers for their jobs ... * Automatic selection of destination printer depending on job option settings * Load balancing on equally suitable printers * implicitclass backend holds the job, waits for instructions about the destination printer of cups-browsed, converts the (PDF) job to one of the destination's (driverless) input formats, and passes on the job. * Highly configurable: Which printers are considered? For which type of printers queues are created? Cluster types and member printers? which names auto-created queues should get? DNS-SD and/or legacy browsing? ... * Multi-threading allows several tasks to be done in parallel and assures responsiveness of the daemon when there is a large amount of printers available in the network.

Found 2 sites for cups-browsed

• https://github.com/OpenPrinting/cups-browsed
• http://www.linuxfoundation.org/collaborate/workgroups/openprinting/cups-browsed

Found 26 RPM for cups-browsed

Generated by rpm2html 1.6

Fabrice Bellet