----- Original Message -----
From: "Nathan Haigh" <[EMAIL PROTECTED]>
.
.
I take it you're having a problem with EU::MM-5.45 which ships with AS build
638, and need to update ? Afaict, updating build 638 by ppm will install
EU::MM-6.05. Is that sufficiently recent for your needs ?
>
> Core modules included with ActiveState distributions go in lib/ of the
> Perl install directory, so to do the modules installed via CPAN.
Only the Core modules (such as ExtUtils::MakeMaker) installed via CPAN will
go into perl/lib. Non-Core modules will go into perl/site/lib .
> However, PPM installs modules in site/lib/.
Yes, so it does .... even for Core modules :-(
I think it's because the ppm gets its files from the blib that's built when
the module is built - and there's no way of telling from the blib alone,
just whether the files are supposed to go into perl/lib or perl/site/lib.
Since most ppm's are for non-core modules, destined for perl/site/lib,
they've probably configured ppm to install to that location. (I'm
speculating on a couple of issues there ... perhaps I'm mistaken.)
> The ordering of directories
> in @INC is such that lib/ is before site/lib/.
As a workaround you can begin your scripts with:
use lib ('C:/Perl/site/lib');
That will place 'C:/Perl/site/lib' ahead of 'C:/Perl/lib' in @INC.
(That's a workaround - not a solution. Perhaps it's satisfactory ... or
perhaps not :-)
> Therefore, trying to
> update modules that come shipped with ActiveState perl using PPM is
> fruitless. They must be installed either via CPAN, which I am trying to
> do for MakeMaker, but am experiencing difficulties (see other posts).
> Or, to install from the source. Is there any way you can Makemaker can
> be forced to install into lib/ rather than site/lib/ when installing via
> PPM?
Not that I know of. There are possibly others here who can give a more
definite answer. Otherwise you could subscribe to ActiveState's PPM mailing
list (see http://listserv.activestate.com/mailman/mysubs ) and ask there.
Specify that you're using build 638, as the answer might be different for
more recent builds.
One other thing to bear in mind is that, just as the 'make install' process
was unable to overwrite one of the MakeMaker files, PPM might also be unable
to overwrite that same file (assuming you find a way to get it to attempt to
install EU::MM into perl/lib).
If you're able to install the version of EU::MM that Michael specified, then
that's probably your best choice .... I haven't tested to see just how easy
it is to install a recent EU::MM into build 638.
Cheers,
Rob
