When I tried to specify a download directory, I got:
The documentation says:
-t DIR, --target=DIR
However, currently cower is looking for "cower -d --target /download/directory (i.e. without the = sign). The documentation example is the standard *nix method (using the = sign with the expanded option) so I like that :).
Also I noticed (and it may be just the PKGBUILD, I haven't looked at it) that the documentation says the example config file is located at /usr/share/doc/cower/config and I found it at /usr/share/cower/config. I think using .../doc/... too is standard but I could be wrong here.
Offtopic: I've been checking out cower and burp and this are really nice, very standard, well-researched programs. Thank you for your work, it has made working with a lot easier.
I don't buy this. cower uses the standard GNU getopt, which allows for an equals sign between a longopt and its required argument:
$ mkdir ~/tmp
$ cower -d cower --target=$HOME/tmp
:: cower downloaded to /home/noclaf/tmp
If you'd like to report that this isn't working, an actual failing example would be needed. It could be any number of things, but I don't suspect cower to be wrong here.
I'm not seeing the doc discrepancy either... version 5 installs to /usr/share/cower/config and references the same in the manpage. Current git head shows both references pointing to /usr/share/doc/cower/config. This was changed in the same commit 46dee5d so I'm not sure what you're looking at. The PKGBUILD doesn't ever explicitly mention the config file.
Ack, my bad on the first discrepancy. I had put it in a bash script and had an error. Sorry, about that.
The second discrepancy comes from the README.pod. I hadn't noticed that the man page and it were different. :)
Well, the README.pod is what generates the manpage. If you're looking at the difference between the manpage on your system and the README.pod in the repo here on github, yes you'll see a difference. I'll do a release at some point, there's some changes that are getting stale...