Re: Verifying File Type Using Only Modules from basic distribution of Perl

Read the source, Luke!

Like all CPAN modules, the source is freely available. You can either install the module yourself in a private directory, and put a 'use lib qw(/path/to/my/lib)' in your program, or as a last resort, copy the source right into your program. The only downside is that these lazy sysadmins create a maintanance nightmare when other people want to use the same module, and/or everyone has their own lib directories taking up disk space.

Update: If the module has no XS component, and consists only of '.pm' file(s), and does not need to be AutoSplit (and File::MMagic seems to qualify), then just the '.pm' file needs to be uploaded (or just copied into your source which you upload).

Comment on Re: Verifying File Type Using Only Modules from basic distribution of Perl

Replies are listed 'Best First'.
Re: Re: Verifying File Type Using Only Modules from basic distribution of Perl by jerrygarciuh (Curate) on Dec 15, 2001 at 02:10 UTC
I thought I would have to have shell access to install the module to a private diretory, no? I have only FTP access to this %^$&%^$& server run by %$^%$ jerks and paid for by my $%%^$ clinet who won't &^*^ listen to me and go with Unix at Hostways. TIA jg _____________________________________________________ If it gets a little bit out of hand sometimes, don't let it fool you into thinkin' you don't care.TvZ	[reply] [d/l]
Re: Re: Re: Verifying File Type Using Only Modules from basic distribution of Perl by mortis (Pilgrim) on Dec 15, 2001 at 02:17 UTC
As long as there are no binary compatability issues, you could build and install it to a local directory structure on your workstation that matches the remote box and recursivly ftp it up (ncftp is great for that kind of thing) to the remote box and just make use of it. It'd be nice if there was some way of building modules localy and 'deploying' them to another box....that might even make a good CPAN module.	[reply]