Problem with LWP when using : to start scripts
Nathan Neulinger (nneul@umr.edu)
Tue, 20 Jan 1998 16:52:39 -0600
On my site, I have several different perl versions installed. I usually
like to have the modules fire off the correct perl depending on which one
they were built with - i.e. h2xs and such.
Second, I have perl stored in a directory that has a LONG path. Normally
people access perl through a symlink, but when installing, the path has
to be specified directly. This doesn't work with #! since it is too long.
However, it works just fine with the : eval exec model.
So, when I build perl, I tell it to exec scripts with the : method.
With the extra scripts in the perl source, this is handled properly,
however with the scripts that LWP installs, this is not handled
correctly, and generates a script that looks like:
-----
: # use perl -w
# $Id: lwp-download.PL,v 1.5 1997/12/03 21:21:00 aas Exp $
=head1 NAME
-----
This won't run at all.
It would be good to add in the eval exec line to handle this case.
-- Nathan
------------------------------------------------------------
Nathan Neulinger EMail: nneul@umr.edu
University of Missouri - Rolla Phone: (573) 341-4841
Computing Services Fax: (573) 341-4216