Re: use lib functionality

hi, k i think i'm starting to see the point. :)

i think my question should have been, is there any difference in uploading a module straight to a path vs. installing a module via the makefile.

i also took a deeper look into the install file of cgi::session and it says the makefile process will do some permission changing...and from what i can tell it just chmod's the files to 755.

thanks every1. i think i'll be all set now.

Comment on Re: use lib functionality

Replies are listed 'Best First'.
Re^2: use lib functionality by AK108 (Friar) on Jun 16, 2007 at 03:05 UTC
With Perl modules that are only Perl code, it is usually OK. When in doubt, try it. Of special note are modules that say they are pure-Perl. This means that the module is a replacement for a module using C, XS, or something similar, so it is often intended to be uploaded without installing.	[reply]
Re^2: use lib functionality by Htbaa (Sexton) on Jun 15, 2007 at 22:50 UTC
My host won't install modules the right way so I have to upload them myself. I've got CGI::Session with only uploading it in a custom lib. But somehow, when using the File driver for session storage I was running into errors. But I'm almost sure it had something to do with running my website under mod_perl and not plain CGI. PS: Don't forget to clean your sessions when they expire :-).	[reply]
Re^2: use lib functionality by wfsp (Abbot) on Jun 16, 2007 at 06:39 UTC
Recent versions of CGI::Session use a recent version of Scalar::Utils. If your hoster doesn't have the appropriate S::U you'll run into the sort of problems Htbaa mentions. I had similar problems myself.	[reply]