Ian Cass wrote:
> Autrijus Tang wrote:
>>> Will this also find modules specified in config files, for example
>>> log4perl.conf, or is this outside the scope of ScanDeps?
>>
>> Well, ScanDeps will find them if you will kindly explain a bit how
>> log4perl.conf should be located and parsed. :-)
>
>
> http://search.cpan.org/~mschilli/Log-Log4perl-0.41/lib/Log/Log4perl.pm
>
> Example...
>
> log4perl.rootLogger=ERROR, LOGFILE
> log4perl.appender.LOGFILE=Log::Log4perl::Appender::File
>
> Careful though, because LOGFILE in the first line is just an alias.
> The 2nd line defines what that alias is. Hence, you can have lots of
> different aliases & associated output modules.
Ooops, sent this mail before I was ready.
Also, to make things a bit more tricky. Log4perl can also parse Log4j (Java)
config files. In this case, the config files look like this
log4j.rootLogger=DEBUG, A1
log4j.appender.A1=org.apache.log4j.ConsoleAppender
which it maps to associated Perl modules. I guess this means you can't just
parse the config files, which in any case, could be installed anywhere.
Good luck :)
--
Ian Cass
