According to Richard Foley <Richard.Foley@m.dasa.de>: :While installing perl-5.6.0-RC2, I thought I'd read the INSTALL docs, I :don't suppose many people do, but there you have it... :-) What kinds of things could be automated as a part of building a 'release', so that before a release the docs can be built for the various formats without error, etc.? Perhaps a script that a) identifies all pod documentation in the release, b) does some sort of 'lint-like check' to see if each pod is properly parseable, and c) some sort of test to see if any doc processing for the particular platform works properly (whether it is pod2man, pod2html, or whatever...). -- Larry W. Virden <mailto:lvirden@cas.org> <URL: http://www.purl.org/NET/lvirden/> Unless explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><-Thread Previous