[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Script interpreter locations



Saying perl is at /usr/bin/perl doesn't solve the bigger problem.  I
can't hard code #!/usr/bin/perl into portable perl scripts because
they might be run on another Unix machine with Perl under
/usr/local/bin/perl or some other location.

Honestly, as a developer I can't care if perl is under /bin, /usr/bin,
/usr/local/bin, or somewhere else.  If my code needs to be portable
across OSes other than just Linux, I have to be prepared for perl to
be anywhere.

Standardizing the location of interpreters in Linux is a good idea,
but realize that developers still have to be prepared fro perl to be
anywhere.

Larry

Andrew Josey writes:
 > On Mar 22, 10:56am in "Re: Script interpret", Daniel Quinlan wrote:
 > > Jakob 'sparky' Kaivo <jake@nodomainname.net> writes:
 > >
 > > > Should there be a standard place to put script interpreters (e.g. perl,
 > > > tcl, python)? There is a thread on the kernel mailing list about a patch
 > > > to support putting things like:
 > > >
 > > > #!perl
 > {bits deleted}
 > > There is a standard place (for perl, sh, csh, etc.) specified by both
 > > FSSTND 1.2 and FHS 2.0.  perl is /usr/bin/perl.
 > >
 > In addition, FHS2.0 in section 4.3 /usr/bin also defines the names
 > /usr/bin/python, and /usr/bin/tcl (as well as /usr/bin/perl)
 > to reference the python and tcl interpreters. These can be
 > symlinks to the physical location.
 > This is tested in the LSB-FHS test suite.
 > regards
 > Andrew
 > -----
 > Andrew Josey                                The Open Group
 > Senior Test Development Manager             Apex Plaza,Forbury Road,
 > Email: a.josey@opengroup.org                Reading,Berks.RG1 1AX,England
 > Tel:   +44 118 9508311 ext 2250             Fax: +44 118 9500110
 > 
 > 
 > -- 
 > To UNSUBSCRIBE, email to lsb-discuss-request@lists.linuxbase.org
 > with subject of "unsubscribe". Trouble? Email listmaster@lists.linuxbase.org


Reply to: