https://bugzilla.redhat.com/show_bug.cgi?id=1953633 --- Comment #16 from Neal Gompa <ngompa13@xxxxxxxxx> --- (In reply to Panu Matilainen from comment #15) > As for the placement, I specifically suggested /usr/lib/debugedit rather > than libexec, because it's traditionally more of a gray area between > /usr/bin and /usr/libexec where all kinds of hard to define stuff lives. > These programs quite certainly are NOT "end user" things, but have > documented interfaces nevertheless and can be called standalone by > knowledgeable users. Which is what I also said in the upstream discussion, > so I'll shut up now :) FWIW, that's fine with /usr/libexec too, that's pretty much what that's for. Putting binaries in /usr/libexec rather than /usr/lib makes it a lot easier for people who want to put noexec on the /usr/lib and /usr/lib64 paths (excluding known systemd paths). -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
