Date: Thu, 3 Feb 2005 15:33:32 -0500 From: Charles Swiger <cswiger@mac.com> To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-stable@freebsd.org Subject: Re: [HEADS UP] perl symlinks in /usr/bin will be gone Message-ID: <48b93f67db4dbc3bcb49c2e1f7e302aa@mac.com> In-Reply-To: <cttsp3$21up$2@kemoauc.mips.inka.de> References: <20050129202425.GA56998@heechee.tobez.org> <20050129220905.46ab86ae.lehmann@ans-netz.de> <41FBFDD9.7070605@mac.com> <cttsp3$21up$2@kemoauc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 3, 2005, at 2:07 PM, Christian Weisgerber wrote:
>> Well-behaved 3rd party scripts ought to start Perl via:
>> #! /usr/bin/env perl
>
> Why should the authors of those scripts break them for systems which
> have /bin/env?
Name one such system. [1]
Hint: the path to env isn't going to change on a standards-compliant
system for the same reason that /bin/sh is always found in the same
place. See IEEE Std 1003.x-2001 ("POSIX").
--
-Chuck
[1]: You might actually find a few very old, very broken versions of
Linux which don't have a /bin/sh, only a /bin/bash. I've heard such
creatures may have a /bin/env rather than a /usr/bin/env, too.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48b93f67db4dbc3bcb49c2e1f7e302aa>
