On Wed, 20 Dec 2006 16:49:29 -0500, Michael Cohen
<micohen us.ibm.com> wrote:
Hi Michael,
>I am really new to the way PPM4 works, so I do apologize
if this seems like
>stupid question. I am trying to update my Perl
libraries, and noticed that
>under the "Upgradable Packages", there are
several listed from the "PERL"
>area. However, that area is locked, and I can only
install the updates to
>the "Site" area. Why can I not unlock the
"PERL" area and update the
>libraries? If memory serves me right, PPM3 and PPM2
allowed me to update
>any library in their orignal locations.
You should not update the modules in the PERL area. They
may be in use
by PPM itself.
>If I upgrade any of these packages, they will all be put
into the "site"
>area. Will this cause a problem? How do I verify the
INC path variable on
>Windows to determine that the "site" path is
searched before the "PERL"
>path?
With the inclusion of PPM4 we changed the order of
directories in INC so
that the SITE area always appears before the PERL area.
We also changed ActivePerl to ship with an empty SITE area;
all bundled
modules are in the PERL area.
This means that PPM4 can now be used to upgrade bundled
modules, and even
core modules by installing later versions into the SITE area
(although the
ActiveState PPM repository does not yet contain updated core
modules).
Previously it would have been impossible to update core
modules, because
PPM2 and PPM3 always install into the site directory, which
was later on
INC
than the standard lib directory for core modules. So even
if you
updated a core module, Perl would continue to use the old
bundled version.
Cheers,
-Jan
PS: You can see the directories in INC in the output of `perl
-V`. Or if
you just want to see INC, please run: `perl -le
"print for INC"`
_______________________________________________
PPM mailing list
PPM listserv.ActiveState.com
http://listserv.ActiveState.com/mailman/listinfo/ppm
|