I have been given severall scripts to maintain. They are packaged in tarballs, and then grouped into more tarballs and then grouped into more tarballs, and they use an installer to install them. The problem that I'm running into is that inside each tarball is an installer script written in perl that has "bad" syntax. I know that the scripts have worked before, but they are barfing now. The "bad" syntax is:

system perl -pi -e s-xxx-`uname -n`- htmlfilename

instead of:

system perl -pi -e s/xxx/`uname -n`/ htmlfilename

Now, since fixing this requires me to open all tarballs and hunt things out I was wondering what I need to do to the environment to make this work instead. Like I said, I know I have used the exact same installer scripts before and they worked, but on the next machine they are not.

And before we get into the "It should be fixed right", it is being fixed right, by the people who have checkin rights, and that means I can't get the package for at least a month (don't ask) and I would like this to work now, without having to go through all the tarballs and find every occurance.

Thanks for your help.

"Nothing is sure but death and taxes" I say combine the two and its death to all taxes!

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.