From the users of the distribution point of view, they installed a piece of software ... when upgrading they expect to have a new version of the software they installed in the past.
Following here the software of the upstream developer whould result ito using 'monitoring-plugins'.
Anyhow ... I have no knowledge about how rpm can handle this. As packager I would maybe do the following for further releases:
* Source package: nagios-enterprises-plugins
* Source package: monitoring-plugins
- Here providing the old 'nagios-plugins-*' packages.
This would give the users the route they decided when they installed their packages mapped to the upstream developers.
From the users of the distribution point of view, they installed a piece of software ... when upgrading they expect to have a new version of the software they installed in the past. plugins' .
Following here the software of the upstream developer whould result ito using 'monitoring-
Anyhow ... I have no knowledge about how rpm can handle this. As packager I would maybe do the following for further releases:
* Source package: nagios- enterprises- plugins
* Source package: monitoring-plugins
- Here providing the old 'nagios-plugins-*' packages.
This would give the users the route they decided when they installed their packages mapped to the upstream developers.