ncdu-zig/doc/Makefile.am

man_MANS = ncdu.1
EXTRA_DIST = ncdu.1 ncdu.pod

# Don't "clean" ncdu.1, it should be in the tarball so that pod2man isn't a
# build dependency for those who use the tarball.
ncdu.1: ncdu.pod Makefile
	pod2man --center "ncdu manual" --release "@PACKAGE@-@VERSION@" ncdu.pod >ncdu.1
Initial import (ncdu-1.1) git-svn-id: svn://blicky.net/ncdu/trunk@1 ce56bc8d-f834-0410-b703-f827bd498a76 2007-07-20 03:15:46 -08:00			`man_MANS = ncdu.1`
doc: Use POD as source format and pod2man to generate ncdu.1 POD is somewhat more simple and flexible. I now use ncdu.pod to generate a nicely formatted manual page on the ncdu homepage, rather than displaying a rendering of ncdu.1 formatted in a monospace font. The tarball will still contain an ncdu.1, so there's no extra dependency on pod2man. (Unless you clone from git, since ncdu.1 isn't in the repo) 2012-01-18 01:34:46 -09:00			`EXTRA_DIST = ncdu.1 ncdu.pod`

			`# Don't "clean" ncdu.1, it should be in the tarball so that pod2man isn't a`
			`# build dependency for those who use the tarball.`
			`ncdu.1: ncdu.pod Makefile`
			`pod2man --center "ncdu manual" --release "@PACKAGE@-@VERSION@" ncdu.pod >ncdu.1`