I am playing with the idea of creating a compiled version of perl with loads of modules that can be installed on a Linux system and used similar to what Strawberry Perl provides for Windows but I have an issue:
After a relocatable perl 5.10 built using -Duserelocatableinc both the scripts that come with perl and scripts that are installed by modules have the following lines at the beginning of the file:
bin/cpan that comes with perl:
#!/tmp/xl/perl-5.10.0-xl-03/bin/perl
eval 'exec /tmp/xl/perl-5.10.0-xl-03/bin/perl -S $0 ${1+"$@"}'
if $running_under_some_shell;
#!/usr/bin/perl
bin/padre that was installed later:
#!/tmp/xl/perl-5.10.0-xl-03/bin/perl
eval 'exec /tmp/xl/perl-5.10.0-xl-03/bin/perl -S $0 ${1+"$@"}'
if 0; # not running under some shell
Once I move the whole installation to some other place these will stop working and I'll
have to write /path/to/new/location/bin/perl /path/to/new/location/bin/cpan
I guess it could be fixed by running an update script after relocating the code but is there a better way that does not require making changes after moving the files?
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.