[HEADS UP] perl symlinks in /usr/bin will be gone
cswiger at mac.com
Sun Jan 30 02:31:31 PST 2005
Edwin Groothuis wrote:
> On Sat, Jan 29, 2005 at 11:51:36PM -0500, Chuck Swiger wrote:
>>Andrew McNaughton wrote:
>>#!/usr/bin/env PERL5OPT='-w' perl
> "#!/usr/bin/perl -w" sounds much easier.
Sure, assuming there actually was a perl in /usr/bin. I would not choose to
hardcode the path to perl when env is available to properly locate the
interpreter for #!-based scripts via the $PATH.
tobez@ is in the unenviable position of trying to support a language that was
added and then removed from the base system. He can produce a port that
respects $PREFIX by not changing anything outside of /usr/local, or one that
provides backwards compatibility with Perl being part of the base system at
the cost of creating extra symlinks and spamming /etc/make.conf.
Since the decision to remove Perl from FreeBSD's base was not accompanied by
universal recognition and acceptance that scripts should not hardcode a path
to /usr/bin/perl, there exists a conflict which is not going to go away until
either Perl gets added back to the base system, or the Perl scripts are fixed.
I don't want to revisit a discussion of whether Perl should be part of base.
I don't want the Perl port to change in a way that breaks existing scripts.
I don't want perl scripts to assume that Perl is in /usr/bin, or
/usr/local/bin, or any other specific place.
I don't want to have perl symlinked between /usr/bin and /usr/local/bin.
I do want scripts to use a portable mechanism to invoke Perl regardless of
where the binary happens to be found, but if people are determined to do
otherwise, well, that's up to them. One solution for those people might be to
install the Perl port with a $PREFIX of /usr rather than /usr/local.
More information about the freebsd-ports