in reply to Website Migration

Hey I am also working on similar requirements. I have lot of scripts running on NT environment and have to migrate to Solaris environment. The following is my points of observation 1. List out all the scripts. 2. Work on one by one. My observation is if the script works on one platform it should work on other with slight modification. 3. Check for paths (// or \\) 4. Most of my migration solved once I looked after path. 5. Though use strict or use warnings helps, you should first understand what the script is doing and from there have to change. Since the developer has left. This way future maintenance will be easy. Hope this helps

Replies are listed 'Best First'.
Re^2: Website Migration
by thezip (Vicar) on Jul 24, 2006 at 20:16 UTC

    One thing i neglected to mention was that the Solaris10 environment change requires that I find all references to /usr/local/www/... and change them to /etc/www/...

    This is required because I do not have *write* access to the /usr/local tree -- its a Solaris "jail" thing.

    The net result here is that I have to find every string or concatenation thereof that evaluates to /usr/local/www/... and then change them to the new path.

    Ugh -- I suspect the potential for breakage is high.

    Where do you want *them* to go today?
      Once you copy the tree into the new environment (maintaining a copy of the original of course), you can run
      find . -name '*.pl' -print0 | xargs -0 perl -pi'.bak' -e 's=/usr/local +/www/=/etc/www/=g'
      This is one of the few parts of the job where having little or nothing in modules makes your job a little easier.

      If you find breakage from this, you can go back and do it again with a more refined substitute, or do further such substitutes. It's a case of Perl helping Perl.

      As others have said, Perl Medic is good. It has good, realisitc advice on strategies, as well as providing tools to help you do the work. Our sympathies are with you.