Should build/install mung the #! line?

J

J Krugman

When a distribution includes executable scripts, should the
build/install procedure mung the first (#!) line of these scripts,
to make sure they match the path to perl in the local system? Or
should this problem be handled by including appropriate manual
configuration instructions in a README or INSTALL file? Is there
a "standard practice" for this?

TIA,

jill
 
B

Ben Morrow

Quoth J Krugman said:
When a distribution includes executable scripts, should the
build/install procedure mung the first (#!) line of these scripts,
to make sure they match the path to perl in the local system? Or
should this problem be handled by including appropriate manual
configuration instructions in a README or INSTALL file? Is there
a "standard practice" for this?

perldoc ExtUtils::MakeMaker:
| EXE_FILES
| Ref to array of executable files. The files will be copied to the
| INST_SCRIPT directory. Make realclean will delete them from there
| again.
|
| If your executables start with something like #!perl or
| #!/usr/bin/perl MakeMaker will change this to the path of the perl
| Makefile.PL was invoked with so the programs will be sure to run
| properly even if perl is not in /usr/bin/perl.

Ben
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,483
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top