Closed GoogleCodeExporter closed 9 years ago
Thanks for the bug report.
It's pretty standard for Unix command-line conventions to allow --no in front of
optional arguments, and not necessarily document them as separate arguments.
There
are other conventions too. For example, a lot of the mysql command-line tools
accept
--skip[foo].
The --help documentation in the Maatkit tools already shows the optional --no in
brackets. It is generated on-the-fly from the POD, and I am thinking that the
POD
should show the same magical syntax with [no] in the option.
Original comment by baron.schwartz
on 10 Dec 2008 at 5:43
Original comment by dan...@percona.com
on 12 Dec 2008 at 4:51
Target these for release end of January 2009.
Original comment by baron.schwartz
on 4 Jan 2009 at 5:04
Here's the change I want to see:
The POD syntax is currently this:
=item --foo
negatable: yes;.....
I want it to be this instead:
=item --[no]foo
Original comment by baron.schwartz
on 4 Jan 2009 at 5:08
I'm working on this. OptionParser will need to be changed of course, because
currently it dies on =item --[no]foo.
Original comment by dan...@percona.com
on 16 Jan 2009 at 9:03
OptionParser updated in r2825.
Original comment by dan...@percona.com
on 16 Jan 2009 at 9:27
I'm working on updating mk-archiver to use pod_to_spec.
Original comment by dan...@percona.com
on 16 Jan 2009 at 10:05
mk-archiver has been updated as of r2827.
Original comment by dan...@percona.com
on 17 Jan 2009 at 6:12
All scripts which had "negatable: yes" have been updated and tested.
Original comment by dan...@percona.com
on 17 Jan 2009 at 9:10
Original issue reported on code.google.com by
dpcah...@gmail.com
on 2 Dec 2008 at 1:18