Well, I went into CPAN and found that I could list all the modules that needed updating so I ran through lots of those. A lot got installed in /usr/local/share/perl/5.8.8.

I just checked my perl version 

lesleyb@fawcett:~$ /usr/bin/perl -v

This is perl, v5.8.8 built for i486-linux-gnu-thread-multi

Copyright 1987-2006, Larry Wall

Perl may be copied only under the terms of either the Artistic License
+ or the
GNU General Public License, which may be found in the Perl 5 source ki
+t.

Complete documentation for Perl, including FAQ lists, should be found 
+on
this system using "man perl" or "perldoc perl".  If you have access to
+ the
Internet, point your browser at http://www.perl.org/, the Perl Home Pa
+ge.

[download]

I have no idea where this newer version of perl might be hiding but I am not picking it up in mormal operations. Or at least what is normal for me ;)

I fixed the cpio upgrade problem by removing Errno.pm and keeping my fingers crossed (and eyes wide shut). The upgrade then worked. What worries me is I have no idea what else is lurking in /usr/local/share/perl/5.8.8 that might come up and bite me later on.

It's not a question of wanting 5.10 on board at the moment. In fact I want the opposite. I would like to keep both the local and remote machine in step and I'm happy to stay on 5.8.8. All I really want to do is upgrade some modules to the latest for my version of perl.

As an example, CGI.pm is two years out of date on Debian stable. The version on Debian stable contains a minor bug which irritates me. I would like to produce to the charset I want or the project requires.

Anyway, at the moment I'm restricting my development to the remote machine so that I develop with what I actually have available on a standard install.

I'm begining to think I need to reinstall perl completely on the local machine just to get back to a known state and I'll have to ask in the appropriate quarters about the feasibility of that. For instance, I have no idea whether the non-existence of perl would break anything in apt-get or aptitude. It would kind of stuff things if it did!

In reply to Re^4: TT2 and FB between two different installations by LesleyB
in thread TT2 and FB between two different installations by LesleyB

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.