in reply to Re: Re: Differentiating between local and system modules
in thread Differentiating between local and system modules

I think I found part of the problem. I've got Pod::Usage declared in ./Foo/config.pm, and when I run myscript.pl from the parent directory, pod2usage() expects to find the --help output POD data in myscript.pl, and doesn't look in ./Foo/Config.pm at all, where the actual relevant POD data exists.

How do I get the POD from ./Foo/Config.pm to show up when I call ./myscript.pl --help (which has a use() specified for 'use Foo::Config;' in it)?

Replies are listed 'Best First'.
Re^4: Differentiating between local and system modules (rtfm)
by Aristotle (Chancellor) on Jun 01, 2003 at 14:10 UTC
    If you read its POD, you'll find mention of the -input option to pod2usage(). That's what you want.

    Makeshifts last the longest.

[reply]
      That seemed to work, thank you Aristotle.

      Along these lines, is it possible to have a more "detailed" output for these arguments, given a POD in ./Foo/Config.pm? Basically I'd like to have the ability to do: './myscript --help' and get the full help synopsis, but './myscript --help foo' would give me only the specific details on the option 'foo'.

      My POD is already quite lengthy, and has quite a lot of options, but paging through them would certainly suck for the end user, since 20k of POD scrolls past them on their screen when they invoke --help on its own.

[reply]

In Section Seekers of Perl Wisdom