Is there a special reason that the "site_perl" folder seems to be searched after the lib: folder? I guess it should be the other way round... Currently it does not seem to be possible to override modules in the "lib" folder by simply placing the newer versions in the respective folder hierarchy level of the "site_perl" folder without removing the versions coming with MacPerl. I realized this after I renamed my "lib extras" folder to "site_perl" and things started to go wrong. Did I miss something? Peter Hartmann Visiting Scholar Ritsumeikan University, Kyoto, Japan e-mail: hartmann@mbox.kyoto-inet.or.jp (preferred) phv00542@askic.kic.ritsumei.ac.jp ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch