You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

28 lines
1.0 KiB

From: olipt at mayo.edu (Travis Oliphant)
Date: Fri, 16 Apr 1999 22:59:25 -0500
Subject: #!/usr/bin/env python -u
In-Reply-To: <cr5yCYgB0KGWFEglFo@holmes.parc.xerox.com>
References: <37175574.25EBDDBE@stuco.uni-klu.ac.at> <cr5yCYgB0KGWFEglFo@holmes.parc.xerox.com>
Message-ID: <Pine.LNX.4.04.9904162255100.22165-100000@us2.mayo.edu>
X-UID: 267
>
> 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?
Sure, since RPM is just a series of sh scripts that run while installing a
package. You could put something in the %post section that did this.
Then the scripts would be set up for whoever ran the rpm command, but not
anyone who didn't have this same enviroment. This would imply multiple
rpm databases on a single system for different users. I'm not familiar
with using RPM in this way but I bet it could be done...
Travis