Date: Wed, 08 May 2002 00:55:43 -0700 From: Peter Wemm <peter@wemm.org> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: Mark Murray <mark@grondar.za>, current@FreeBSD.ORG Subject: Re: The future of perl on FreeBSD Message-ID: <20020508075543.A5E5838CC@overcee.wemm.org> In-Reply-To: <Pine.NEB.3.96L.1020507202743.83455K-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: > First question is -- people are going to be upgrading FreeBSD. Having a > stale /usr/bin/perl is going to muck stuff up royally. Likewise, many > existing scripts use /usr/bin/perl at that location. Can we simply have a > symlink that points /usr/bin/perl at /usr/local/bin/perl (and any related > pseudo-programs such as suidperl, etc) as part of the normal install along > with the perl package. Likewise, it would be good to clear out the lib > stuff if we can to prevent the inevitable breakage there during the > upgrade. If we hook symlink creation into the build, that would also > force us buildworld/installworld'ers to install the package, which would > improve exposure. Do Perl applications typically hard code paths, or just > rely on Perl to "know where to look"? We have several choices.. From installing a symlink pointing to wherever the default perl package is, through to a simple redirector that searches $PATH and/or looks in a few well-known locations. Heck, python often uses "#! /usr/bin/env python". This works for perl scripts too. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020508075543.A5E5838CC>