Yes, that's what I've been using up to now. The problem is that I have the development version on my network, but I also want to run the code on a notebook that may not be connected to the network. Since different machines have different system drives (the one I'm working on uses F:, for example), I'd prefer to avoid paths that would need to be machine specific.
John, yes, you have a different situation than I have. The environment variable method may work best for you. I just installed Citrus Perl 5.16 and in trying to run a wxPerl screen capture script I found on Perl Monks, a required module couldn't be found in the "standard" @INC paths. After locating the module several levels deeper in the directory structure, I used the use lib to point to it. As I learn more, I may have to change plans also. I'm looking at putting commands into .profile to set things up at login.