Probably

I’ve just had a horrible time trying to install Catalyst::Plugin::AutoCRUD, because of a dependency on WWW::Mechanize. In short, WWW::Mechanize fails to pass it’s tests when you’re working behind an authenticating proxy. (continue reading…)

As much as I like Solaris the packaging system is crap. And fathoming out what package you need to install to gain a particular command is nigh on impossible. (continue reading…)

In my earlier post about using local::lib I commented that CPAN wouldn’t untar with the Solaris shipped tar program, and you had to use GNU tar from OpenCSW or Blastwave. 1.94 appears to fix the problem and untars just fine with the native Solaris tar. (continue reading…)

In my last post about installing Catalyst on Solaris I went to great lengths to install every Perl module, in order, from CPAN. This was a painful process to establish, and just as painful to emulate. The post was updated back in March to include CPAN bundles, which would do most of the hard work for you – but as was pointed out in the comments, it should’ve been a simple case of ‘cpan Catalyst’. (continue reading…)

I tend to build perl modules to live in my home directory. Setting up CPAN with PREFIX= and LIB= variables means I can compile/build modules without being root and use them in any script with a simple ‘use lib …’ statement. (continue reading…)

I decided to take a look at Catalyst on Solaris. Having done a bit of work with it on Mac OSX, I discovered it wasn’t that easy to get going on Solaris with the stock Perl. Even using cat-install from ShadowCat didn’t render the easy result I’d experienced using MacPorts. After a few hours battling with CPAN, I’ve managed to come up with this list of modules to get Catalyst up and running. (continue reading…)