On Mon, Jan 31, 2005 at 10:42:28PM -0500, Ian D. Leroux wrote:
> The subject line says it all: since the pkg_alternatives wrapper script
> is itself a #!/bin/sh script, and since execve(2) only goes through one
> such indirection, python scripts starting with #!/usr/pkg/bin/python get
> treated as shell scripts, with predictably erratic consequences.  So is
> this usage deprecated or is there an accepted solution?  The package
> lang/python (now defunct) didn't have this problem because it used a
> symlink instead of a wrapper script.

Weird... what's the rationale behind this?  I mean, why is the python script
treated as a shell script at last?

-- 
Julio M. Merino Vidal <jmmv@menta.net>
The NetBSD Project - http://www.NetBSD.org/