29 lines
971 B
Plaintext
29 lines
971 B
Plaintext
From: janssen at parc.xerox.com (Bill Janssen)
|
|
Date: Sat, 17 Apr 1999 01:28:04 GMT
|
|
Subject: #!/usr/bin/env python -u
|
|
In-Reply-To: <37175574.25EBDDBE@stuco.uni-klu.ac.at>
|
|
References: <37175574.25EBDDBE@stuco.uni-klu.ac.at>
|
|
Message-ID: <cr5yCYgB0KGWFEglFo@holmes.parc.xerox.com>
|
|
X-UID: 1266
|
|
|
|
Martin,
|
|
|
|
I'm not a big fan of the /usr/bin/env approach for Python scripts,
|
|
because at PARC many people run without having Python on their paths.
|
|
Many, many packages at PARC, including Python and ILU, are installed in
|
|
their own directory tree under either /project (/project/ILU/) or
|
|
/import (/import/python-1.5/). People enable or disable various
|
|
packages depending on what they're up to.
|
|
|
|
So I tend to depend on GNU configure when I'm installing a script. I
|
|
actually look for Python in the user's environment, then use sed to
|
|
hard-code that path into the scripts before installing them. Can this
|
|
be done with RPM?
|
|
|
|
Bill
|
|
|
|
|
|
|
|
|
|
|