in reply to Re: Re: Re: commented out s/// prevents script running!
in thread commented out s/// prevents script running!

ok, figured out a way of getting 5.8.3 invoked instead of 5.8.0 .. but, and this is a big but, *cries* do I _have_ to install all of my modules again??!
  • Comment on Re: Re: Re: Re: commented out s/// prevents script running!

Replies are listed 'Best First'.
use autobundle
by Tomte (Priest) on Mar 03, 2004 at 14:56 UTC

    Fire up perl5.8.0 -MCPAN -e shell and use autobundle to create a Bundle for your old installation; fire up perl5.8.3 -MCPAN -e shell and install the created Bundle (Something like Bundle::Snapshot_2004_03_03_00.pm), lean back and let perl do the work ;-)

    regards,
    tomte


    Hlade's Law:

    If you have a difficult task, give it to a lazy person --
    they will find an easier way to do it.

Re: commented out s/// prevents script running!
by jonadab (Parson) on Mar 03, 2004 at 14:43 UTC
    figured out a way of getting 5.8.3 invoked instead of 5.8.0 .. but, and this is a big but, *cries* do I _have_ to install all of my modules again?

    Short answer: yes.

    Longer answer: if the modules don't use XS, you might be able to avoid re-installing them by messing with @INC, but this is probably not recommended if you don't know what you're doing. Fire up perl -MCPAN -e shell and install your modules again -- that's the easy way.


    ;$;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b->()}} split//,".rekcah lreP rehtona tsuJ";$\=$;[-1]->();print
      5.8.3 is supposed to be binary-compatible with 5.8.0, so if you configured it to include the 5.8.0 directories (and built it with the same options) it shouldn't be necessary to your modules.