Bug 868051

Summary: RFE: emit version string on execution with no command
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: CSProcessorAssignee: pressgang-ccms-dev
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.xCC: lcarlon, lnewson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-19 00:42:23 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 Joshua Wulf 2012-10-19 00:35:48 UTC
To check what version of csprocessor is installed / running on a machine, it would be useful to be able to just do: 

csprocessor

currently this returns a help screen,  but no version information. executing a command outputs the version, as does --version.



==============================
Generated Details:

Package: cspclient-0.27.6-1.noarch

OS: Fedora release 16 (Verne)

Comment 1 Lee Newson 2012-10-19 00:42:23 UTC
If you want the version then you should use "csprocessor --version", that's the whole point of that command. If you put an invalid option in (or no option), then it should show help options. As such I see no use for this and you haven't provided any reasoning for this RFE. If you can provide a valid use case outside of not wanting to type "--version" then I'll reconsider.

Comment 2 Joshua Wulf 2012-10-19 06:20:26 UTC
I frequently do bug testing of builds of the csprocessor, and use it on multiple machines. Ascertaining which version is installed / active is a frequent activity, and I regularly find myself issuing "csprocessor" with an /expectation/ that it will give me its version - because other programs that I frequently use do that.

Reporting version along with usage information when invoked with no arguments is a standard design pattern. 

For example:

jwulf@radhe Node-dev]$ nmap
Nmap 6.01 ( http://nmap.org )
Usage: nmap [Scan Type(s)] [Options] {target specification}
TARGET SPECIFICATION: [...]

Adding that doesn't do away with the --version argument. For example, that argument is useful for determining the available version of csprocessor in a script by parsing the output.

Hopefully that makes the rationale clearer.