Red Hat Bugzilla – Bug 164963
plague-client bogus 'usage' text
Last modified: 2008-08-02 19:40:35 EDT
Description of problem:
plague-client's "usage" on "email" doesn't match with implementation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
<command> is one of:
build [package_name] [cvs_tag | srpm_path] [target]
list <email> <status>
# plague-client list email@example.com needsign
Error: invalid option 'firstname.lastname@example.org'
Apparently, the correct command syntax is:
plague-client list email <email>
plague-client list email <email> <status>
doesn't seem to work at all.
# plague-client list email email@example.com needsign
Error: invalid options.
I didn't write plague-client or much of plague at all.
Dan did. There's no need to convey possession of it anyway.
the format that seems to work is:
plague-client list email firstname.lastname@example.org status needsign.
(In reply to comment #1)
> I didn't write plague-client or much of plague at all.
> Dan did. There's no need to convey possession of it anyway.
I didn't mean to accuse anybody - You're just the person bugzilla assigns
buildsys PRs to.
> the format that seems to work is:
> plague-client list email email@example.com status needsign.
OK, then somebody might want to change plague-client's usage to
list email <email> [status <status>]
or whatever the "correct" usage is.
I wasn't taking it as an accusation. I just wanted to give credit in the right
Now about the change. I think it might be maybe more worthwhile to make the
interface more optparsing:
plague-client --email=foo --status=bar list
Dan, what do you think?
Ralf, does that make sense to you?
(In reply to comment #3)
> Ralf, does that make sense to you?
Actually, I would propose to apply
i.e. short options + (optional) long options.
IMO, this also is the essence also recommended by
Patches accepted for getopt :)
This bug hasn't been updated in a long time and targets FE devel.
Could you please check that it still occurs with current FE devel and update
Bug seems to be fixed.