Description of problem: Help should be patched to use right command name: In Fedora, 'ninja-build' is used for both name the package and the command, instead of just 'ninja' as in the help output. So either rename package only or patch the help also. Hmm, there is the ninja IRC client that conflicts of course. Version-Release number of selected component (if applicable): ninja-build-1.4.0-1.fc20.x86_64 (Verified on Fedora 20, but I think this is also for Rawhide with v1.5.x) How reproducible: yes Steps to Reproduce: 1. yum install -y ninja-build 2. ninja-build --help 3. Actual results: usage: ninja [options] [targets...] Expected results: usage: ninja-build [options] [targets...] -or- do not rename command and just use 'ninja' as the original name. Additional info: A patch should be easy to do.
CC to maintainer of ninja IRC.
Created attachment 971746 [details] ninja-build for help output
This is somehow related to #1166135
(In reply to Raphael Groner from comment #2) > Created attachment 971746 [details] > ninja-build for help output Hmm, a good patch could be more tricky than expected: Do not trust argv[0], http://www.lst.de/~okir/blackhats/node40.html
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Reverting back to rawhide. This is an issue with packaging. The binary name gets modified intentionally in spec file and independently from any version.
ninja (jabber client) is orphaned and upstream of it seems to be dead. Therefore, maybe consider to rename ninja-build back into ninja.
(In reply to Raphael Groner from comment #7) > ninja (jabber client) is orphaned and upstream of it seems to be dead. > Therefore, maybe consider to rename ninja-build back into ninja. Yes, as docker-io has been renamed to docker finally ;)
Ping, any news here?
I have a patch to update the binary name, testing it with a local build now. As for renaming it, see Bug #1166135.
Was fixed in 1.6.0-3.