Subject: Re: @INC order Date: Wed, 30 Oct 1996 00:00:16 -0500 From: ScottRCHLG@aol.com To: Martin.Cleaver@bcs.org.uk Martin, What you have sounds interesting. Could you send me a copy of Perllib.pl? Thanks, Scott Smith --------------- In reply to -------------------- Date: Sun, 20 Oct 1996 00:32:52 +0800 From: Martin RJ Cleaver To: Nick Ing-Simmons CC: perl5-porters@africa.nicoh.com Subject: Re: @INC order References: <199610181432.QAA15540@dxmint.cern.ch> <199610181542.QAA02202@pluto> Nick Ing-Simmons wrote: > > Lionel Cons writes: > >I strongly prefer to have the "site" libs before the "normal" libs in > >@INC so that one can hide a library from the Perl distribution with > >one in the site area. > > Oh no, not again .... > > I strongly prefer to have "site" library the "stable" version [...] Sure. This is what I use to allow me to switch between a development environment and a production environment. Also included are three sets of libraries: standard (i.e. from cpan), adhoc (for stuff that I write or from friends, and override (that which is supplied in the standard distribution but I consider broken.). Arguably, the override directory should be versioned in line with the distribution of perl. This allows me to incorporate new versions of libraries very easily. I have a command that alters my environment without me needing to edit anything - it alters the Windows Registry but could equally alter a symlink or change a file to alter variables that control my environment. c:\win32app\ perl5\ (original, untouched version) perl-extra-libs\ dev\ adhoc\ override\ standard\ LWP\ IO\ prod\ adhoc\ override\ standard\ LWP\ IO\ I use the command 'perllib' thus: perllib prod prod dev (standard from prod, adhoc from prod & override from dev) Simple, but really handy for managing multiple environments. I'll send Perllib.pl if anyone is interested. Regards, Martin. -- Martin.Cleaver@BCS.org.uk