in reply to renaming a package

I have to agree with dragonchild on this one and say that you probably are going to save yourself trouble in the long run if you just go back and fix code that calls your module by the old name. OR you could freeze the module in place at a point in time and just migrate code that needs the changes made to your newly renamed module.

You could edit your old scripts by running something like:

find . -depth -name '*.p[lm]' | xargs perl -spi -e 's/Log::Writer/MWLOG/'
CAVEAT:Completely untested.

Replies are listed 'Best First'.
Re: Re: renaming a package
by mifflin (Curate) on Apr 30, 2004 at 19:25 UTC
    It would be nice to change all those programs but the environment I work in would require formal test plans for each, and there are alot of them.
    Just thinking about the amount of paper work it would produce makes me dizzy.

          Just thinking about the amount of paper work it would produce makes me dizzy.

      Sounds like my shop. Then I'd just leave the older scripts on the old version until they required an upgrade and change them then.