We've been asked to "standardize" our strawberry perl path (make it the same as activestate, "c:\perl64\perl.exe"). The ugly part of this is that moving the contents of c:\strawberry\ one directory higher results in c:\win32 c:\cpan c:\licences and other undesirables.

One option would to simple copy perl.exe to c:\perl64\ as well as leaving it in the normal strawberry directory. A concern is that we will break any scripts using $^X to find prove, wperl.exe or anything else out of the bin directory. Who does this anyway? Does anyone have any other ideas what might go bang if we do this?

We're also weighing up other options: recompiling perl, using a junction, and copying everything from the bin directory



- Boldra

In reply to Copying the Strawberry perl.exe by Boldra

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.