Scenario: A previously shipping RPM has the capability to be built with
diagnostic and other debugging features. This has always been turned off
and should be turned off for any production deployment. However the
ability to install a version of the package with these features enabled
would be immensely useful.
Here is how I thought I would do this: add a "diagnostic" subpackage
that includes only the binary with the diagnostic build. There will be a
file conflict only on the binary and users will have to look for the
diagnostic subpackage to ascertain which build is executing.
What is the best way to add alternate builds in an RPM? Do we have
existing precedent? I didn't find any guidance in the packaging
guidelines, the closest I could find was the "Conflicts" doc
) which didn't really
address the issue.