On Wed, Jul 7, 2010 at 10:01 AM, Joshua ben Jore <twi...@gmail.com> wrote:
> What? That's certainly not what happens for me. I just ensured I had
> no ~/.cpan or ~/perl5, installed perlbrew, then installed new
> perl-5.12.1. When I ran the newly created cpan client, my default `o
> conf yaml_module' is YAML and not Parse::CPAN::Meta. I just tried
> requesting an upgrade to CPAN and my client is already up to date
> (1.94_56).

There are two situations in which CPAN.pm reads YAML files.

(1) A distribution contains META.yml or produces a MYMETA.yml after
running Build.PL/Makefile.PL -- in this case, Parse::CPAN::Meta is
preferred and CPAN.pm will fall back to the configured 'yaml_module'
setting if Parse::CPAN::Meta is not installed or if Parse::CPAN::Meta
throws an error during parsing.

(2) CPAN.pm is reading distroprefs or its own cached data --  in this
case CPAN.pm uses the configured 'yaml_module' (which is also used to
create the cached data files)

-- David

Reply via email to