Thanks for the suggestion. Compiling my own perl build was really a last
ditch option I regarded as admitting defeat, i.e., fixing / finding the
actual problem wa deemed to difficult.
Late last night, after going through the build logs in much greater detail,
I noticed that a number of packages were asking for module builder of a
recent vintage. Turns out that this was the root of the problem. Module
builder needed to update itself, however, somewhere along the line, module
builder broke its ability to update itself more than one point release at a
time. Once I fixed this, Catalyst updated just fine.
On Feb 13, 2012 1:48 AM, "Kieren Diment" <firstname.lastname@example.org> wrote: > On 13/02/2012, at 1:32 PM, Evan Carew wrote:
> > I have the older Catalyst packages for my stock FC12 laptop installed,
> > I've failed to upgrade them twice already. The question I have is what's
> > the best way to get the latest Catalyst installed on my linux box. Do I
> > need to clear out perl entirely, and start from scratch, or is there some
> > not-so-well-known procedure besides CPAN to upgrade to the latest.
> 1. Compile your own perl to /usr/local/bin or a relocatable perl
> 1a If relocatable also install and configure local::lib (mainly because of
> shebang issues and relocatable perl) (optionally install and configure
> local::lib anyway).
> 2. Update your PATH variable if necessary.
> 3. Install App::Cpanminus.
> 4. Leave the system perl alone for system utilities.
> List: Catalyst@lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive:
> Dev site: http://dev.catalyst.perl.org/