https://bugzilla.redhat.com/show_bug.cgi?id=1884608 --- Comment #7 from Patryk Obara <dreamer.tan+fedora@xxxxxxxxx> --- @Kamil Páral Thank you! :) I wasn't even aware there is "Conflicts:" tag, that can be used. URL with updated spec: https://raw.githubusercontent.com/dosbox-staging/dosbox-staging/bdb5d0685bd7d0d2da0b0f1f88006c526e8124bf/contrib/fedora/dosbox-staging.spec diff: https://github.com/dosbox-staging/dosbox-staging/commit/bdb5d0685bd7d0d2da0b0f1f88006c526e8124bf I think in this case we're ending up in following rule from the guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/Conflicts/#_incompatible_binary_files_with_conflicting_naming_and_stubborn_upstreams: > (…) 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. In this case, I don't think users are interested in having both dosbox and dosbox-staging installed at the same time. The only usecase for doing so is development/regression testing - and for that developers are likely to build their own version of DOSBox (either from SVN or our mirror branch in Git). Once fcami will have a moment to review the spec file, we probably should add "Conflicts: dosbox-staging" to dosbox package as well. --- I explained why we kept the binary name (and consequently the man page) in this comment: https://github.com/dosbox-staging/dosbox-staging/issues/664#issuecomment-718856147 We could use "alternatives" mechanism, but I prefer to do it only if users actually request this... https://docs.fedoraproject.org/en-US/packaging-guidelines/Alternatives/ (using this would require alternating binary, man page, and probably patching desktop entry) -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
