At the moment, fail2ban may sometimes print a message on install reminding you that you should install pyinotify or gamin in order to use those polling methods, that you need python[sqlite] in order to use the persistent database feature, and that you need systemd[python] in order to track logins from the systemd journal. While this is moderately useful it still requires a bit of fiddling when I'm doing a reinstall to get right. This is a request to add four new use flags to net-analyzer/fail2ban, pyinotify, gamin, sqlite and systemd, which would activate the appropriate dependencies, as follows: pyinotify -> dev-python/pyinotify gamin -> app-admin/gamin sqlite -> dev-lang/python[sqlite] systemd -> sys-apps/systemd[python] (looking at the existing dependencies, this one may be unnecessary) This would allow such dependencies to be expressed in package.use files, instead of having to remember to install the packages manually, or add them to the world file, where they don't exactly belong. Reproducible: Always Steps to Reproduce: 1. Install net-analyzer/fail2ban Actual Results: Various optional dependencies were not installed. Expected Results: Optional dependencies should be installed based on use flags.
These sound like runtime-only deps. As of right now, there is a policy-level ban on using USE flags to specify runtime-only deps in packages. I'm assigning it to the maintainers of fail2ban, but likely this bug will be closed RESO/INVA for the reason above.
I see, thank you. Basically, I was thinking about in terms of, for example, the vim-syntax use flag, which seems very similar to this.
The ebuild tells you what to do to get things working the way you want. So that might mean setting USE=sqlite on dev-lang/python. You want the ebuild not to say that but instead set USE=sqlite on net-analyzer/fail2ban, and then re-emerge two packages instead of one. How is that progress?
