| 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.
This is a special case of "Dist::Zilla::Plugin::Prereqs::MatchInstalled" that automatically upgrades all versions of all dependencies, unless asked not to. PITFALLS Presently, there is one very large gotcha about using this module, in that it will upgrade everything, even things that don't make sense to upgrade. For instance: Local Versions If you have a single dependency on your system you might use, which is locally patched, and locally patched in such a way the local version is more recent than any on "CPAN", you should either a. Not use this module b. Put that module in the exclusion list Non-Dual Life modules This plugin is not very smart, and can't differentiate between modules that do exist on "CPAN" independent of Perl, and modules that don't. For instance, if you use "Autoprereqs", its very likely your distribution will add a dependency on either "strict" or "warnings" This module will ask your user to upgrade those versions to their latest versions, which will likely require them to upgrade their Perl installation to do so. Which basically means for the mean time, either a. You must be o.k. with end users needing more recent Perls b. You should avoid upgrading those dependencies by either a. Not using this plugin b. Adding problematic modules to the exclusion list
Generated by rpm2html 1.6