Date: Sun, 30 Jan 2005 14:44:38 +0100 From: Matthias Andree <matthias.andree@gmx.de> To: Matthias Andree <matthias.andree@gmx.de> Cc: tobez@freebsd.org Subject: Re: [HEADS UP] perl symlinks in /usr/bin will be gone Message-ID: <m3is5fav5l.fsf@merlin.emma.line.org> In-Reply-To: <20050130030837.GA87780@falcon.midgard.homeip.net> (Erik Trulsson's message of "Sun, 30 Jan 2005 04:08:37 %2B0100") References: <20050129202425.GA56998@heechee.tobez.org> <20050129220905.46ab86ae.lehmann@ans-netz.de> <m3fz0jtzbc.fsf@merlin.emma.line.org> <20050130030837.GA87780@falcon.midgard.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Erik Trulsson <ertr1013@student.uu.se> writes: >> Hardcoded paths in scripts are a mess. What if I installed Perl into >> /opt/mumble on some other machine? /usr/freeware? /what/ever? Changed >> $PREFIX and/or $LOCALBASE? > > Then you would have nobody but yourself to blame. So ports not heeding PREFIX or LOCALBASE aren't buggy? Interesting POV. > And what about all the scripts that administrators and users write that > are not part of any port? Scripts that were written according to the > de-facto standard that having '#!/usr/bin/perl' on the first line of > the script will work correctly. As mentioned before, #! /usr/bin/env perl is the canonic SHORT way to run perl, longer ways are in perlrun(1). -- Matthias Andree
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m3is5fav5l.fsf>