So, what I think I'm hearing you suggest -- is that rather than trying to get yahoo to install a perl module into it's /usr/bin/perl structure on all their web servers -- it's possible to build a stripped down perl with all the modules required built right into it, and upload that package and all the related files somewhere in the path I own, and then somehow point to that build rather than the default for the yahoo server?
Now to be more specific, I build something like citrusperl on my laptop or wherever, add the CPAN perl modules I need to that, then use cavapackager to build a binary package that I can upload to somewhere in the tree to my site? Then I guess I change the path to the new perl instance in my script to use my version of perl somehow? I anticipate that I would need some symbolic links at worst...
Is that the idea? -- thank you for sticking with me on this by the way, I do appreciate it...
It seems like I could install cygwin somewhere without perl, then install citrusperl, cava package it, upload it to yahoo, test it, and keep the cygwin environment because I will probably wish to add functionality over time. Then I just refresh the upload whenever I add a non-standard module, and back in business for more? correct?
In reply to Re^6: Scrape Yahoo Financial Historical- Process Dataset - format and create dynamic page
by tbone654
in thread Scrape Yahoo Financial Historical- Process Dataset - format and create dynamic page
by tbone654
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |