Zabbix SIA publish their agent packages using the name `zabbix-agent` while they are listed in EPEL as `zabbix<ver>-agent`. It is also quite common for installers to repackage the agent with yet another name with their own custom scripts, plugins and configuration.
I write an agent module package (https://github.com/cavaliercoder/libzbxpgsql) which currently requires that `zabbix-agent` first be installed. Unfortunately, users who install the EPEL package fail to satisfy this requirement, despite the agent binaries being deployed in an appropriate way.
To reproduce this issue, install any version of the Zabbix agent from EPEL, and then attempt to install the libzbxpgsql package and it will fail with unresolved dependency `zabbix-agent`. If the Zabbix SIA provided package is used instead, the issue is resolved.
Could the package maintainers please consider adding a `Provides: zabbix-agent` declaration in the EPEL `zabbix*-agent` packages? This way, the EPEL packages will satisfy (via virtual package) the requirement from any 3rd party module package for `zabbix-agent` to be installed.
I considered using `Require: /usr/sbin/zabbix_agentd` instead, but this limits other packagers of `zabbix-agent` from installing binaries in other locations. For example in my case, the binary is deployed to `/opt/zabbix/sbin/zabbix_agentd`.