+ Keep in mind that implicit conflicts are NEVER acceptable. If your package conflicts with another package, then you must either resolve the conflict, or mark it with `+Conflicts:+`.

+ Packagers should keep usage of `+Conflicts:+` to a bare minimum. Only upgrading from two previous release of Fedora is supported, so Conflicts against older packages than that, while technically correct, are unnecessary, and should not be included.

+ In the specific case where multiple software components generate identically named (but incompatible) binaries, Fedora Packagers should make every effort to convince the upstreams to rename the binaries to resolve the conflict (see: xref:#_binary_name_conflicts[Binary Name Conflicts]). However, if neither upstream is willing to rename the binaries to resolve the conflict, *AND* the binaries are not viable candidates for alternatives or environment modules (incompatible runtimes), as long as there are no clear cases for both packages to be installed simultaneously, explicit Conflicts are permitted at the packager's discretion. Both packages must carry Conflicts in this case.

+ If the library is 100% ABI-compatible, you can use xref:EnvironmentModules.adoc[Environment Modules] to let the user switch between them. If the library is not 100% ABI-compatible get one of the upstreams to rename. See xref:#_approaching_upstream[Approaching Upstream] for ideas on persuasion. If neither upstream will budge open a ticket for FPC to evaluate what sort of hoops both packages would need to implement to not conflict at runtime.

+ * In the case where the conflicting binaries provide the same functionality, you can then rename the binaries with a prefix, and use xref:Alternatives.adoc[Alternatives] to let the system administrator select which generic name is the default. Note that this is usually not the case.

+ * In cases where the binaries provide similar functionality xref:EnvironmentModules.adoc[EnvironmentModules] may be an option. This is more flexible than alternatives and is for things that each individual on a system may want to choose between rather than a system administrator.

+ Just as files can conflict, package names can as well. Conflicting package names *MUST* be resolved. Package names which differ only in case are still considered to be conflicting. You should follow the same basic steps outlined in xref:#_approaching_upstream[Approaching Upstream].