From: Marilyn Sander > On May 26, 2010, at 3:35 PM, Shawn H Corey wrote: >> On 10-05-26 05:41 PM, Marilyn Sander wrote: >>> What would be the preferred practice here? >> >> See `perldoc lib` >> > Thanks, this document just explains about @INC. I already > know how to use @INC. My question was about "normal", > "standard", or "best" practice for placement of scripts > and Perl libraries on Windows. The default setup for > ActiveState is to put site-specific stuff into > c:\Perl\site\lib. I would rather use a location on the > network, mapped to a network drive. I know how to do that, > I just want to know if Windows people would find that weird > or objectionable.
There is very little in the way of standards, normality or best practices in the MS-Windows world. It really doesn't matter what you do as long as you document it so that others can understand it. ActiveState and Cygwin each have their own ideas about where to put files, and they are not necessarily compatible. I haven't tried Strawberry Perl, but Camelbox also has a unique directory structure. I would be more concerned about making sure I can restore each system after a hard drive failure. .bat was the old MS-DOS script extension. I always put those files in C:\Belfry. Just make sure they are in the %PATH% or all of your scheduled events and scripts use absolute paths. The only other issue is to make sure your base scripts record errors when there are network problems and they can't reach those servers. Notice I said 'when' not 'if'. It is a basic theorem that there will be times that your scripts can't get through. Bob McConnell -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
