Actually, I am a bit more selective in my Linux system, where I do leave alot out, with my mirror as a source. But it, as a development system which I try to make fully usable *offline* is heavily loaded so as to run or compile virtually anything.
The Win7 system is a bit different in design, but when I seen how sneaky the ActiveState PPM system was, I decided to go whole hog, and just install everything for the day when they decided to paywall everything, as they are doing now by trying to deprecate PPM snd not doing any noticeable updates in quite some time. I would actually do a bunch of pruning to any 'uninstalled' list to get rid of cruft like AWS, CGI, Locales, and modules for proprietary services and utils. I dont mind older modules, as I have a collection of thousands of perl scripts that I dip into to use as templates for projects I might need at a whim. And I typically want to be able to use their modules. As well as use the Site dirs as a library. Its easier than going through CPAN or ls -lr and trudging through the Author dirs.
Its how I learn Perl, and other languages. Reading books doesnt seem to sink in.
So heres my issue: I can chop down the autobundle easily enough (to say, around 10,000). But the darn thing has version numbers. Will it install those *old* versions? If so, I can take the file and process it to just get the modules names, parse them into blocks of 250, and send a block at a time to CPAN. (After removing existing duplicates).
| [reply] |
Since you are going to use Strawberry perl and cpan as your package repository this seems to be a moot point don't you think? Even AS perl ships with a cpan client by default, and build tools can be installed/configured. I wouldn't waste the time to install even 10,000 modules at once, it makes much more sense to simply install the one you known you need right now, or any that perl tells you are mossing when you run one of your scripts. minicpan makes it easy to create and maintain a mirror you can use offline or on your local network.
| [reply] |
The point is, I do everything I can to avoid the cloud when possible.
For data, and even multimedia (I D/L and dont stream!)
I have learned all too well that what is on the net one day, may be gone the next. Here we even archive news articles to print->PDF or actual paper.
In Debian I have had some favorite apps deprecated and removed (but faithfully retaianed in my archives, plus mirror).
In Debian I have also been known to append the Site dirs of older Perl installs to the end of perlenv.
I dont write enterprise apps, just useful scripts for my systems and ecommerce website, and believe that if it works: DONT FIX IT. Even if its from 1998.
One of the nicer things with Perl, as opposed to Ruby/Python is the relative lack of versioning hell. Just update everything, and if necessary set the 'use' version at the top of the scripts/modules. There is no real downside to 'extra' modules. I use the notest pragma becuase the tests can be damn obscure, and in Win I fully realize that most scripts are written for Unix and make allowances accordingly. Even with MingW.
Its the relative 'freedoms' allowed with Perl that I simply dont migrate everything to Python, which is much easier to read and understand, though its a PITA with text from what I have seen. Nothing beats the $_ =~ s/foo(bar)/baz$1/ig 'sugar'.
| [reply] |