On 19 May, 15:41, [EMAIL PROTECTED] (Steffen Mueller) wrote:
> m.nooning schrieb:
>
> > > BEGIN {require foo; require bar;...}
>
> Just an idea: if you don't want to actually load the module but include
> a hint for Module::ScanDeps to pick up the dependency, you can do this:
>
> sub _wont_ever_be_run {
> require Foo;
> require Bar;
> # ...
>
> }
>
> If you just don't call _wont_ever_be_run, it won't load the modules
> since require() happens at run-time. But the static dependency scanner
> of Module::ScanDeps can pick up the require statements just fine.
>
> I suppose wrapping the require()'s in an if (0) {} block works as well.
>
> HTH,
> Steffen
This is all great stuff and I do thank you all.
It does beg the question though, if I'm using a module such as
Crypt::OpenPGP how do I find out what other modules it needs (i.e. the
modules that are missing and require manual inclusion)?
Sorry if I'm being dim.
Thanks
