Bug 1298801

Summary: dnf inline help not coherent across commands
Product: [Fedora] Fedora Reporter: Francois Rigault <rigault.francois+fed>
Component: dnfAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 23CC: jsilhan, mluscon, packaging-team-maint, pnemade, vmukhame
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-19 14:46:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Francois Rigault 2016-01-15 06:19:23 UTC
Description of problem:

got me while wanting to disable a repo

    dnf config-manager
    (no answer)
    dnf config-manager --help
         --enablerepo [repo]
         --disablerepo [repo]
    (no detail on those two options, assume they do what I want)

the --help option, even displayed *after* the command name, will always show the general options. I found after that this the correct way to get help on a command:

    dnf help install

Also for config-manager this help is most unhelpful. In fact one would have to type

    dnf config-manager --help-cmd

to get the relevant options from config-manager

Currently on Fedora23 x86_64


Steps to Reproduce:
1. dnf config-manager --help is not helpful
2. dnf help config-manager is not helpful
3. dnf config-manager --help-cmd is never mentioned in dnf help page


Expected results:
--help option last line should be "Run dnf help command to get help on a command", at least if a command was specified

dnf help config-manager should give something meaningful


Additional info:
would it make sense to link to readthedocs.org in dnf output?

Comment 1 Honza Silhan 2016-01-19 14:46:36 UTC

*** This bug has been marked as a duplicate of bug 1158548 ***