(In reply to Sam Kottler from comment #24)
> I agree that it's too early to decide on the issue. These are the packages
> in EPEL that depend on nagios-plugins and what do we want to do about them?
Dunno if rpm have a 'provide', but if, I would add such a provide to the corresponding binary packages. This would be "nagios-enterprises-plugins" and "monitoring-plugins" as long as both are compatible.
> Create community-plugins-* alternatives?
This isn't a bad idea at all, as those plugins aren't either from Nagios Enterprises, LCC nor from the Monitoring Plugins Project. If there are projects maintaining a larger set of plugins those should maybe get it's own source package.
(In reply to Sam Kottler from comment #24)
> I agree that it's too early to decide on the issue. These are the packages
> in EPEL that depend on nagios-plugins and what do we want to do about them?
Dunno if rpm have a 'provide', but if, I would add such a provide to the corresponding binary packages. This would be "nagios- enterprises- plugins" and "monitoring- plugins" as long as both are compatible.
> Create community-plugins-* alternatives?
This isn't a bad idea at all, as those plugins aren't either from Nagios Enterprises, LCC nor from the Monitoring Plugins Project. If there are projects maintaining a larger set of plugins those should maybe get it's own source package.
Cheers, Jan.