Re: [rt.cpan.org #119737] Problems with detecting DateTime::Format::Natural dependencies

Thu Jan 12 16:10:01 2017: Request 119737 was acted upon.
Transaction: Correspondence added by [email protected]
       Queue: Module-ScanDeps
     Subject: Re: [rt.cpan.org #119737] Problems with detecting DateTime::Format::Natural dependencies
   Broken in: (no value)
    Severity: (no value)
       Owner: RSCHUPP
  Requestors: [email protected]
      Status: resolved
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=119737 >


On 12.01.2017 20:26, Roderich Schupp via RT wrote:
> <URL: https://rt.cpan.org/Ticket/Display.html?id=119737 >
>
> On 2017-01-09 06:20:59, [email protected] wrote:
>>>> Interestingly, in this case the double colon notation did not work.
>>> What exactly didn't work? I tried the following:
>>> pp -o natural.exe -u -M DateTime::Format::Natural:: \
>>>      -E 'use DateTime::Format::Natural;
>>>          my $dt = DateTime::Format::Natural->new-
>>>> parse_datetime("tomorrow");
>>>          say "tomorrow is $dt";'
>>>
>>> This works,
>> I am getting an error reported by eval that it cannot find
>> DateTime/Format/Natural/Lang/EN.pm, if I add ' -M
>> DateTime::Format::Natural::Lang::EN.pm'.
> Hmm, "-M DateTime::Format::Natural::" is supposed to add DateTime/Format/Natural.pm
> and every *.pm below DateTime/Format/Natural - that should have included
> DateTime/Format/Natural/Lang/EN.pm.
>
> Cheers, Roderich

I thought the same thing.

The only explanation I have is that no file in DateTime/Format/Natural 
has use .*EN in it. EN.pm is somehow imported in a different way which I 
have not had the time to figure out yet. However when I use pp -c, it 
works without any -M parameters so I am going to use that in the future.

Cheers and thanks a ton for the help and the fix!

Till