Date: Sun, 30 Jan 2005 12:18:17 +0100 From: Kirill Ponomarew <krion@voodoo.oberon.net> To: Mark Sergeant <msergeant@snsonline.net> Cc: freebsd-ports@FreeBSD.org Subject: Re: [HEADS UP] perl symlinks in /usr/bin will be gone Message-ID: <20050130111817.GC62253@voodoo.oberon.net> In-Reply-To: <06d669a96d0ca3a9e026f564e0422598@snsonline.net> References: <20050129202425.GA56998@heechee.tobez.org> <1985053043.20050130134456@serebryakov.spb.ru> <200501301208.19650.raabe@kde.org> <06d669a96d0ca3a9e026f564e0422598@snsonline.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 30, 2005 at 09:11:34PM +1000, Mark Sergeant wrote: > >find /some/directory -type f -print0 | \ > > xargs -0 perl -pi -e 's,^#! ?/usr(/local)?/bin/perl,#!/usr/bin/env > >perl' > > > > One problem I always had with "env" or equivalents... what happens if > someone manages to polute $PATH with a perl that is not infact perl but > something else, I remember being taught "Always specify full paths to > binaries, especially in cron". /usr/local/bin is default path in $PATH on FreeBSD, so problems like "what if it isn't perl, but something else" should be resolved by users/admins. -Kirill
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050130111817.GC62253>