|Index||index by Group||index by Distribution||index by Vendor||index by creation date||index by Name||Mirrors||Help|
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.
When rpmfind is asked for a resource it first asks the local RPM base, and if it's not available, will request the associated RDF file on a remote database. The result describes the various packages providing these resources (distribution, vendor, version, date, etc...). Based on that information, rpmfind sorts the various packages for suitability. Then it picks the first one and fetchs more complete information like the dependencies required by this package. It then verifies that all the dependencies needed by this package are available, and recusively trys to locate RPM providing uninstalled resources. At the end rpmfind shows the list of packages to fetch and the total size needed on disk. The database can be built using rpm2html.
|rpmfind-1.7-4mdk.i586.html||Locate and transfer automatically RPM using HTTP and an RDF database||Mandriva 10.1 for i586||rpmfind-1.7-4mdk.i586.rpm|
Generated by rpm2html 1.6