This is very much an issue of the way your Unix environment is built. You can always build a module in your home directory for testing, but running production code with a dependency on your home directory is arguably a very broken dependency. If you need to use the module out of your home directory, just add a "use lib" statement to your script, which will modify the @INC variable (which tells perl where to look for modules).
[EMAIL PROTECTED] wrote: > > Hellohello! > > I don?t have the root permissions for the server that I?m running my > scripts from, and I need a module that does not exist on the server. > > One way is to ask for the administrator to add the module to the server, > but is there any other way to resolve this problem? Like install the > module to my home directory or something in that way? > > _______________________________________________ > Perl-Unix-Users mailing list > [EMAIL PROTECTED] > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
begin:vcard n:Bell;Bayard tel;work:(212) 762-1035 x-mozilla-html:TRUE org:Morgan Stanley;Distributed Systems Integration version:2.1 email;internet:[EMAIL PROTECTED] title:UNIX Dork adr;quoted-printable:;;9th Floor=0D=0A750 Seventh Avenue=0D=0A;New York;NY;10019;USA x-mozilla-cpt:;-19088 fn:Bayard G. Bell end:vcard
