On Mon, May 13, 2002 at 02:45:09PM -0600, Lyndon Nerenberg wrote:
> >>>>> "Jonathan" == Jonathan Perkin <[EMAIL PROTECTED]> writes:
> 
>     Jonathan> An auto-configuration script which merely checks for the
>     Jonathan> existance of a file rather than actually testing it's the
>     Jonathan> file it needs is a bit silly and probably deserves the
>     Jonathan> breakage.
> 
> And just what else besides Perl would you expect to find in
> /usr/bin/perl you silly pedant?!? ;-)  

A broken symlink?  Perl 4?  Perl 6?  A perfectly reasionable wrapper
script?  If these programs detect perl and don't work because the
wrapper is there, then a) they are broken and b) it will only take a
couple minutes to fix by adding a perl package so why worry.

/usr/bin/perl should work if perl is installed to avoid a massive POLA
violation.  Since ports must not touch /usr/bin and we must not assume
that PREFIX=/usr/local, a symlink is out of the question.  A wrapper
isn't really going to cost us anything performance wise and allows the
possability of providing something more useful then "File not found"
as an error message.  As such, it's a very good solution.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

Attachment: msg38295/pgp00000.pgp
Description: PGP signature

Reply via email to