| 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.
In any sufficiently-sized application or framework, it's common to end up lumping a lot of different concerns into the same class. For example, you may have business logic, persistence code, and UI all jammed into a single class. Attribute and method names for all sorts of different operations get shoved into a single namespace -- even when using mixin classes. Separating concerns into different objects, however, makes it easier to write reusable and separately-testable components. The AddOns package (``peak.util.addons``) lets you manage concerns using ``AddOn`` classes.
| Package | Summary | Distribution | Download |
| python-peak-util-addons-0.7-6.el7.noarch.html | Dynamically extend other objects with AddOns | EPEL 7 for ppc64le | python-peak-util-addons-0.7-6.el7.noarch.rpm |
| python-peak-util-addons-0.7-6.el7.noarch.html | Dynamically extend other objects with AddOns | EPEL 7 for aarch64 | python-peak-util-addons-0.7-6.el7.noarch.rpm |
| python-peak-util-addons-0.7-6.el7.noarch.html | Dynamically extend other objects with AddOns | EPEL 7 for ppc64 | python-peak-util-addons-0.7-6.el7.noarch.rpm |
| python-peak-util-addons-0.7-6.el7.noarch.html | Dynamically extend other objects with AddOns | EPEL 7 for x86_64 | python-peak-util-addons-0.7-6.el7.noarch.rpm |
Generated by rpm2html 1.6