Hello,

I'm running Bugzilla on an Apache Linux server here at work. We want to do some customization of the product to better suit our needs. I have everything set up in CVS and it's running on the server and all is well. Now, when I check it out of CVS and start working on it locally (on a WinNT machine), all of the #! lines are pointing to the server's version of Perl (/usr/local/bin/perl). This of course doesn't exist locally. My question is this, what is the best practice for dealing with this situation? I'm sure lots of people have run into this and I'm curious as to the solutions. The only solutions I could come up with are:

- Manually change each Perl script's #! line (which amounts to 12-15 scripts). And then remember to change them back when versioning.
- Create Ant check-out and check-in scripts that will modify each Perl file and change accordingly.
- Create the /usr/local/bin/perl directory on local machines.

I like the Ant scripts option the best of these three, but am wondering if there's something better out there.

I'm open to all ideas!
Thanks!
Trent

Retitled by Steve_p from 'Best Practices Question...'.


In reply to Dealing with incorrect shebang line entries on Windows with Apache by tohann

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.