NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
ethan (3163)
ethan
reversethis-{ed. ... rap.nov.olissat}
Being a 25-year old chap living in the western-most town of Germany. Stuying communication and information science and being a huge fan of XS-related things.
reversethis-{ed. ... rap.nov.olissat}
Being a 25-year old chap living in the western-most town of Germany. Stuying communication and information science and being a huge fan of XS-related things.
Thursday May 20, 2004
02:33 AM
Administrating sf's compile-farm
This morning I installed the following modules on Sourceforge's compile-farm (Mac OS X machines, for now):
- MailToos
- MIME-Base64
- File-Temp
- Storable
- WeakRef
- IO-stringy
- FileHandle-Unget
- MIME-tools
- Mail-Mbox-MessageParser
Needless to say, it is perl5.6.0 so I had to live with a few test failures. Also, each module requires to be uploaded via scp to the shell server and from there to cf.sf.net. I also noticed that those must be the world's slowest computers running Mac OS X. It takes anything between 5 and 15 seconds to extract a single tarball.
I tweaked the environment a bit so now PERL5LIB always points to my private tree of installed modules. It feels almost like home now.
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Administrating sf's compile-farm 0 Comments More | Login | Reply /