Issue #198 has been updated by Garrett Honeycutt. Status changed from Closed to Re-opened Target version deleted (0.25.0) Affected Puppet version changed from 0.25.4 to 2.6.1 Keywords set to man manpage
The puppet man page appears to be a one line static entry. Our goal should be to have it dynamically generated. I suggest that we take the approach that git uses, since it correlates well with the puppet commands. Here is a snippet from man -k git <pre> git (7) - the stupid content tracker git (rpm) - Core git tools git-add (1) - Add file contents to the index git-am (1) - Apply a series of patches from a mailbox git-annotate (1) - Annotate file lines with commit info git-apply (1) - Apply a patch on a git index file and a working tree </pre> We could have entries for puppet, puppet-apply, puppet-resource, etc. ---------------------------------------- Bug #198: puppet does not have a manpage https://projects.puppetlabs.com/issues/198 Author: Redmine Admin Status: Re-opened Priority: Normal Assignee: Luke Kanies Category: documentation Target version: Patch: None Affected Puppet version: 2.6.1 Keywords: man manpage Branch: Seeing this, http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/109214 I'm sure it's already on a TODO list somewhere, though I didn't see it in Trac. For short term purposes, I've had great success writing a small POD file (even for non Perl apps, no source, just POD) and running pod2man on it. pod2man --center="foosball" --release="" foosball.pod | gzip -c > foosball.1.gz -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
