https://bugzilla.redhat.com/show_bug.cgi?id=2231216

Tadej Janež <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
              Flags|                            |needinfo?(errornointernet@e
                   |                            |nvs.net)



--- Comment #13 from Tadej Janež <[email protected]> ---
@[email protected],

thanks for creating this review request.

I quickly looked at the SPEC file and I think it one issue will be the
conflicting names of binaries and manual pages.
This is expected since par2cmdline-turbo is effectively a fork of the
par2cmdline.

The Fedora Packaging Guidelines's section on Common Conflicting Files Cases and
Solutions
(https://docs.fedoraproject.org/en-US/packaging-guidelines/Conflicts/#_common_conflicting_files_cases_and_solutions)
recommends to talk to upstream maintainers and ask them to rename the binaries
(and manual pages) to avoid the conflicts.

Naturally, we could teach users how to create symlinks or aliases so they can
use par2cmdline-turbo as a drop-in replacement for par2cmdline.


-- 
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2231216

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202231216%23c13

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to