Since it is no longer possible to find the running executable from the
call stack, docs have to be kept somewhere in the source tree.
Of course, at this point, we shouldn't be using RDoc::Usage at all.

This adds the --charset option to puppetdoc for RDoc mode.
This allows to set the charset for the generated html.

Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>

Change the --help text to match the new single executable invocations

Signed-off-by: Jesse Wolfe <jes5199@gmail.com>

Signed-off-by: Luke Kanies <luke@madstop.com>

Requires the pandoc binary to function (http://johnmacfarlane.net/pandoc/).

Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>

There is currently two type of documentation generation
for manifests (module or modulepath):

 * RDoc HTML generation for modules and global manifests
 * console output for sole manifest

Both version handles classes, defines, nodes, global
variable assignements, and resources when --all is used.

The usage is the following:

For the rdoc variant:
$ puppetdoc --mode rdoc --outputdir doc
It uses the puppet.conf configuration file to get the modulepath
and manifestdir settings. Those are overridable on the
command line with --modulepath and --manifestdir.

For the console output version:
$ puppetdoc /path/to/manifests

Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>

reference), and adding error handling to puppetdoc.

class for Parameter, which apparently lost the 'nodoc' method
for that class.