Has anybody in the audience run into this type of problem and solved it with a local Module installation? If so, what type of procedure would I need to follow to install the necessary files from my home Windows machine, into my remote Apache driven web server? As I understand it, most Perl installations use a command line interface, which I don't have access to (no telnet or ssh permissions). I FTP to my website via WS_FTP Pro. I have CGI, PHP and SSI privileges within my own website, but cannot go above my own root folder (no access to the Linux OS).
My shebang statement is: #!/usr/bin/perl
This is used by the rss2html.pl script
If I manage to install the missing RSS module locally, how do I call it from the script?
As you can tell I am not a Guru in Perl, just a user.
Thanks for your bearing with me on this, and any help you may be able to offer me.
Wiz
I have been using Javascript includes from a service that is about to go strictly commercial. All of the newsfeeds will be removed in a few weeks, and I am looking to display the ones I want, via XML links to rss files.
Wiz
Well, perhaps this will get you started...
How do I install Perl modules? [perl.com]
1) Download from cpan
2) Decompress and untar
3) run perl Makefile.PL
4) make
5) In your Perl scripts at the top of them:
BEGIN {
push (@INC, "/full/path/to/XML::RSS/Module");
}
==============
This will set the scripts to look for the Perl modules in that location as well as the default/system locations.
Then just use the module as you normal would. Its a simple process.
use XML::RSS
BEGIN {
push (@INC, "/full/path/to/XML::RSS/Module");
}==============
This will set the scripts to look for the Perl modules in that location as well as the default/system locations.
That is precisely what I needed to know, if I am going to go to the trouble of tarring and feathering this Perl Module into my website. Thank you!
Wiz
BEGIN {
push (@INC,"/full/path/to/custom/mods");
}
Will create problems due to the quotes thus if you experience this issue simply remove the quotes:
BEGIN {
push (@INC,/full/path/to/custom/mods);
}
Don't forget you can include variables too:
BEGIN {
push (@INC,$custom_path);
}
Our company gets tired of having to setup the same parameters over and over and over thus we have created a general library file and link against it for common vars - like sendmail paths, admin e-mails, etc. It doesn't work for all scripts but it helps with general administration.
I'd love to know, but wouldn't like to try it out without knowing more - I'm a bit unfamiliar with this type of coding :)