Summary: | sys-apps/portage: repoman feature suggestion: user-supplied additional checks ("plugins") | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Andreas K. Hüttel <dilfridge> |
Component: | Repoman | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andreas K. Hüttel
![]() ![]() For now, you can add a class inside /usr/lib/portage/pym/repoman/checks.py and add it's name to the _constant_checks variable that's near the bottom. If we implement the ~/.repoman/usertests/ idea that you suggest, then you'll have to put python files in there which contain classes like those in checks.py. I may end up working on this for work; we will see. I am currently near the end of the repoman rewrite stage2 which is the modularization and plugin system stage. But, modules are not quite plug and play. Many of them are dependant on other modules being run before and needing data provided by them for later checks. As part of stage3 of the rewrite, I will work on making that configurable via a config file. Once that is done, you will be able to install an optional module and configure it into the correct run slot. To be fully plug and play would mean creating a dependency system for module run order. I'm not sure if that will be worth it, also it will add to the run time. repoman support has been removed per bug 835013. Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist. |