This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: Heads-up: postinstall scripts and PATH (Attn all package maintainers)
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Harold L Hunt II <huntharo at msu dot edu>
- Cc: cygwin-apps at cygwin dot com
- Date: Tue, 24 Feb 2004 15:36:08 -0500 (EST)
- Subject: Re: Heads-up: postinstall scripts and PATH (Attn all package maintainers)
- References: <Pine.GSO.4.56.0402241406210.13702@slinky.cs.nyu.edu><403BB395.8040303@msu.edu>
- Reply-to: cygwin-apps at cygwin dot com
On Tue, 24 Feb 2004, Harold L Hunt II wrote:
> Igor,
>
> So, can I get an example of how to do this setting of the PATH? Is it
> as easy as:
>
> PATH=/bin
>
> ???
Almost. IMO, it should be
PATH=/bin:$PATH
export PATH
instead. But I may be wrong, and there may be no reason to keep the old
$PATH value. You do need the "export", though.
> Is it going to be a problem to have "#!/bin/bash" or "#!/bin/sh" at the
> top of the script? If so, what should that be instead?
>
> Harold
No, as long as the explicit path to an executable is used (i.e.,
"/bin/sh" rather than "sh"), it's ok.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton