--On Mittwoch, Mai 02, 2007 14:53:24 -0400 "(Andreas J. Koenig) via RT"
<bug-CPAN@rt.cpan.org> wrote:
Show quoted text> I'm surprised, this does not match my observations. There must be
> something going on that I do not know of.
Hi again,
just for documentation purposes I quote some from my answer to #26886.
As I carelessly did not state in the initial report, I did not use the CPAN
shell, but a script to report changelogs.
A sketch of what it does (including the workaround for #26886):
Show quoted text> $m=CPAN::Shell->expand("Module", "IO::Socket::SSL");
> $f=$m->cpan_file;
> $d=CPAN::Shell->expand("Distribution", $f);
> if (!defined CPAN::Distribution::dir($d))
> { CPAN::Module::get($m); }
> $dir=CPAN::Distribution::dir($d);
> # look in $dir for Changes, Changelog, ChangeLog etc. ...
Show quoted text> How large is your build_cache? What does CPAN.pm say, when you start
> the shell and then do your first install or test or make command?
build_cache =
'build_cache' => q[100],
'build_dir' => q[/root/.cpan/build],
'build_dir_reuse' => q[1],
'build_requires_install_policy' => q[ask/yes],
...
'scan_cache' => q[atstart],
(atstart was already set before I did "o conf init").
Show quoted text> I agree that there should be a way to invoke the manager cleanup
> routine. Currently it is only invoked on new invocations of the shell.
> And not by batch jobs. Ahhh, I see, this is probably much closer to
> what you need, right?
Not sure about that. Up to version 1.8802 and using
$CPAN::Config->{'scan_cache'}='atstart', the build cache cleanup was
triggered automatically just by using my changelog reader. I think it would
not hurt if this behaviour was re-instated. Otherwise I would need to write
code depending on CPAN version in the script.
Best regards
Matthias
