Why does PPM install core modules such as ExtUtils::MakeMaker into 
site/lib/ rather than lib/? This behaviour together with lib/ appearing 
before site/lib in @INC results in not being able to upgrade such 
modules using PPM, but rather you have to install them through CPAN 
which I would think is a pain for a lot of people since you need a make 
utility. Is the intended behaviour? If so, what is the rationale behind it?

I'm trying to install ExtUtils::MakeMaker > = 6.06 since it includes 
fixes for when the command line length limit is exceeded in windows - 
such as by large test suites in large modules. I'd like to make a ppd 
for this when I've done, but this problem would make it useless.

Thanks
Nathan

p.s. please let me know if this is not the behaviour in a particular 
version of PPM/ActivePerl as it must have slipped me by.
_______________________________________________
PPM mailing list
PPM@[...].com
http://listserv.ActiveState.com/mailman/listinfo/ppm