in reply to Managine local modules

If all you're looking to do is to load the module with the newest version you may want to consider ex::newest. However, if your sole goal is to have your script check all other directories before the local lib directory, there may be an easier way: If you're use()-ing lib;, you may want to consider pushing into @INC, since perl transverses @INC as an array to find module- see perldoc -f require. Or you could also just go by hand, and remove the module from existance, which is a cumbersome possibility.

Of Note: Ingerson's module, which may be helpful as well, is only .
Gyan Kapur
gkapur@myrealbox.com

Replies are listed 'Best First'.
Re: Re: Managing local modules
by moseley (Acolyte) on May 02, 2003 at 14:41 UTC
    Thanks, ex::newest looks like what would be closest. I suppose there's a minor performance hit for looking more through @INC.

    I can't just alter @INC because now my local perl library has modules that are both newer and older than the installed ones.

    I guess I just have this desire to have a nice clean local perl library of just the modules I need -- and once the site-wide library contains a newer version of some module I'd like to purge my local library of the older version.

    Thanks again for the pointer to ex::newest.