Hide Forgot
Hello. Currently every build for each RHOS release contains just a el7ost suffix. This means we cannot do the builds with the same version-release for different RHOS release versions. Consider adding RHOS' version as well. E.g. "%{dist}" should look like "ost9", "ost10", "ost11", and so on.
less invasive approach - provide a macros which contains RHOS distribution version. In this case %{dist} remains intact (containing el7ost), and we will use new macro for that. Something like "%{?rhosdist}".
This has been discussed in the past and rejected. We have many packages that don't change across releases or are updated for all releases concurrently (mariadb, rabbit, python dependencies, etc). yum provides ways to determine which repo a package came from. As a general rule, I think we should avoid the situation where we're doing multiple builds for multiple releases that have the same NVR except %dist. If the contents between the versions is different, then we should reflect that with different numbering schemes. For example: rabbitmq-server-3.6.3-5.el7ost for osp 9 rabbitmq-server-3.6.3-6.el7ost for osp 10 If we must update osp 9 without going to -6 for OSP 10 (say we need 1 patch out of 2 backported), we should be doing rabbitmq-server-3.6.3-5.1.el7ost instead of rabbitmq-server-3.6.3-6.el7ost9